DI_PCP_Protheus_PPI_Multitask_Integration

PCP Protheus x PPI-Multitask Integration

Business Context

1. Manufacturing Execution Systems, or simply MES is the term used to refer to the systems focused on the management of production activities establishing a direct link between planning and shop floor. The MES systems generate precise information and in real time promoting the optimization of all production stages since the issue of an order to the shipment of finished products shipment.
   The importance of these systems comes from the gap that regularly exist between the ERP (Enterprise Resource Planning) and the specific softwares of the production line.  The MES can import data from ERP and integrate with the production daily routine, managing and synchronizing the productive tasks with the flow of materials.
   Considering that in the supply chain the highest added value is in the production, it makes sense investing in systems optimizing the flow, control and quality of material (Source: PPI-Multitask).
2. Planning and Production Control  Gathering of means of production (raw material, labor, and equipment) enables manufacture of products that arise from the action of productive systems. The plans are the guide of execution and in production control are commanded by the auxiliary body named Planning and Controlling of Production (PCP) that establishes the production line rules, aiming at an ordered and continuous flow of the productive process.
3. Shop Floor Allows you to plan, punch and monitor activities executed in each work center of the plant and machine, enabling an integrated view of executed operations, under execution and to be processed.  Allows the Management and Monitoring of results (productivity, efficiency, delays, quality, use, levels of downtime, scrap reason, deviation of real/standard time etc). In MES integrated use, punches are executed by MES system.

Systems Involved

• PCP PROTHEUS 11.80.14, 12.1.10 (Phase I)
• PCP - SIGASFC PROTHEUS 11.80.17 (Phase II)
• PC-FACTORY (PPI MULTITASK)

Integration

The aim of the PC Factory Integration (MES software of company PPI Multitask) X PROTHEUS is to make available to TOTVS customers a new option to control the production through the automation of processes, enabling the updating and extraction of online information to simplify the customers flow.

Scope

Enables the integration between the PCP module of SIGASFC Protheus with MES PC-Factory of PPI Multitask, aiming at controlling the annotation of production orders. Protheus is responsible by the creation of production orders and the PC-Factory with annotation.

The integration contemplates the following routines and processes in PHASE 1:

1. Parameterization: Enables to parameterize the use of integration, indicating if it is ACTIVE. Indicates whether there is generation of XML files of information that is transferred between the systems, and also enables to define filters that are applied to information.
2. Integrators: Adapters are functions responsible for sending or receiving information that is transferred between Protheus and PC Factory systems. Integration contemplates the following information: Product, stock location, resource, production orders, production annotation and stoppage annotation.
3. Pendencies: Enables to manage the pendencies of PCP Protheus delivery to PC-Factory as well as to check the history and errors of integration process.
4. WebService: Enables to process the annotation of production and stoppage sent from PC-Factory to Protheus;
5. Synchronization: Enables to execute the synchronization of data from PCP Protheus and PC-Factory. Able to send data from Products, Stock Location, Resource and Production Order.
6. Import Log: Enables to query the integration process of annotation of production and stoppage sent from PC-Factory to Protheus.

The integration contemplates the following routines and processes in PHASE 2:

Phase 2 contemplates the consumption of components, movements executed by PC-Factory and balances in stock. It also considers the SIGASFC - Shop Floor system.

1. Parameterization: Enables to parameterize the use of integration, indicating if it is ACTIVE. Indicates whether there is generation of XML files of information that is transferred between the systems, and also enables to define filters that are applied to information.
2. Integrators: Adapters are functions responsible for sending or receiving information that is transferred between Protheus and PC Factory systems. Integration contemplates the following information: Product, stock location, resource, machine, tools, script, structure, address, production order, balance in stock, movements and transfer of stock, annotation or production and stoppage annotation.
3. Pendencies: Enables to manage the pendencies of PCP Protheus delivery to PC-Factory as well as to check the history and errors of integration process.
4. WebService: Enables to process the annotation of production and stoppage sent from PC-Factory to Protheus;
5. Synchronization: Enables to execute the synchronization of data from Protheus and PC-Factory. Able to send data from Products, Stock Location, Resource, Machine, Script, Structure, Address, Balance in Stock and Production Order.
6. Import Log: Enables to query the integration process of annotation of production, refusal and stoppage sent from PC-Factory to Protheus.

Install/Implement/Use Requirements

For Protheus version 12, apply package of updates from version 12.1.10 in Phase I. It can also be used in version 11.80.14 for Phase I and 11.80.17 for Phase II. Run the update of dictionary with program U_UPDPCP34.
Build must be equal to or later than 7.00.131227A and date 9/8/2014.
IP Address and released port for WebService execution. These data are used in APPSERVER.INI file in session WEBSERVICE.
Update APPSERVER.INI  file in session WEBSERVICE.
To configure a WebService, check this configuration: http://tdn.totvs.com/pages/viewpage.action?pageId=6064937
Exemplo :
; WEBSERVICE CONFIGURATION

[WebServices]
Enable=1
Environment=mssqlserver
Conout=1
Trace=1
PrepareIn=99,01
NameSpace=http://10.80.62.219:8090
URLLocation=http://10.80.62.219

[HTTP]
enable=1
port=8090

[ONSTART]
JOBS=JOB_WS_9901

[10.80.62.219]
ENABLE=1
Trace=1
PATH=C:\TOTVS 11\Microsiga\Protheus_Data\web\ws
ENVIRONMENT=mssqlserver
INSTANCENAME=WS
RESPONSEJOB=JOB_WS_9901
DEFAULTPAGE=wsindex.apw

[JOB_WS_9901]
TYPE=WEBEX
ENVIRONMENT=mssqlserver
INSTANCES=1,20
SIGAWEB=WS
INSTANCENAME=WS
ONSTART=__WSSTART
ONCONNECT=__WSCONNECT

;FIM CONFIGURACAO WEBSERVICE

You can also update in APPSERVER.INI file in session PROXY (if there is configured proxy)

[PROXY]

Enable=1
Server=proxy-jv.jv01.local
Port=8080
User=XXXXX
Password=*******

Installation/Updating

The PCP Protheus x PC-Factory PPI-Multitask is activated through the following steps:

1. Open the progrm of Integration Parameters: PCPA109 (Updates -> Integration MES-> Parameters).
2. Set the field Active to "1- Active".
3. In the field path enter the URL of WebService of PPI-Multitask.
4. Check WebService connectivity through Test button.
5. Indicate whether the integration physically generate the XML files.
6. Configure the filters for each information that is transferred between the systems.
7. Confirm the activation through the button CONFIRM.

The Test button check whether you can execute the connection with WebService entered in the field Path. This button has two returns:

• Connection with WebService successfully executed.
• Unable to execute the connection with WebService of PCFactory.

Selecting the field Generate XML, the XML of the exchanged messages is generated. If you do not select it, the system saves it only in tables. You are not required to create files. It works as a useful tool to find problems and it can be saved in XML directory successfully sent or pending XMLs.
The file names follow these standard:

OK_<MSG>_<DATAHORA>_<REGISTRO>
PEND_<MSG>_<DATAHORA>_<REGISTRO>
ERR_<MSG>_<DATAHORA>_<REGISTRO>
Where: OK - Message sent with no problems
           PEND- Message not sent
           ERR - Message sent, but returned with error.
          MSG - Name of message. Ex.: Item, Wharehouse, Workcenter, etc.
           DATETIME: Date and Time of sending
           RECORD: Record code being sent. Ex.: Item code, order number, etc.

For each file moved (product, stock location, resource, tool, machine, script, structure, address, movements, balances and production order) a folder exists. For each folder, you can assemble filters and define parameterizations. These filters are used in routines that send PC-Factory information enabling you to select what must be sent. The fields of selected table (folders) and operators are displayed so filters are assembled. If there is no filter registered, every record added, edited or deleted is sent to PC-Factory. To assemble the filters, the user must know the database, as table names and fields are directly used.
Example:
To assemble a filter, so only products classified as Finished Product are sent. Filter is: B1_TIPO = "PA"

The delivery of Protheus information for PC-Factory PPI Multitask, the following transactions occur:

• Register, change and deletion of product MATA010, AGRA045 stock location and MATA610, SFCA006 and SFCA002 resource;
• Register and change of orders MATA650;
• Process to FIRM orders MATA651;
• Maintenance of operations MATA632;
• Maintenance of allocation, MATA380 and MATA381;
• Register, change and deletion of Operations x Components MATA637;
• Machine Load MATA690;
• Calculation of MRP MATA712 (version 11.8) or PCPA107 (version 12);
• Register, change and deletion of structure, MATA200;
• Production splits generated by routines that handle order, and SFC310 annotation model 1 of shop floor.
• Register, change and deletion of address MATA015;
• Register, change and deletion of tools MATA015;
• Balance Update
• Inbound Invoice - Routines executing function B2ATUCOMD1;
• Sales Invoice - Routines executing function B2ATUCOMD2;
• Internal Movement - Routines executing function B2ATUCOMD3;
• Addition of balance MATA220 and MATA805.

The delivery of PCP-Factory PPI Multitask information for Protheus, the following transactions occur:

• Register of stoppage reasons SFCA004;
• Register of scrap reasons SFCA003;
• Stock Separate movements. Inbound MATA250. Outbound MATA240;
• Transfer of stock MATA261;
• Annotation of production MATA681 and SFCA310;
• Annotation of stoppage MATA682 and SFCA311;
• Refusal, annotation of loss, MATA685.

Version Control

TOTVS group, represented by its brands, manages the layout progress demands and other adjustments, agreeing together with requesters the release approval term.
All progress scheduled must be discussed and approved by brands before the start of development and is only developed in case of agreement of brands and alignment with directive defined by TOTVS Integration Committee.

Support

All lines are responsible for support to integration resources; hence, the support teams of RM Connector and Protheus® Back Office products are ready to make the first analysis and, whenever needed, to transfer it to the fittest team in each case.

Transactions/Entities/Singles Messages

The following transactions are exchanged between TOTVS and PPI-Multitask:

Information Flow

Transactions information flow:

• Product, stock location and resource: during creation, change and deletionof a product in program MATA010, from a stock location in program AGRA045 or of a resource in programs MATA610 or SFCA006 or SFCA002 (machine) and tools in MATA620. The programs check whether the integration is active, and if positive, they deliver the register to PC-Factory. If there is no error, the register does not display any message, if there is an error, a message is displayed questioning whether to create a delivery pendency in program PCPA110. If you choose to operate a pendency, the process is committed in Protheus, and the updating for PC-Factory must be executed through PCPA110.
  In the engineering, the register of structure MATA200 and script MATA632 or MATA637 and addresses MATA015 are integrated whenever a record is created, changed or deleted.
• Production order: during creation and change of a production order, or during the change of the status of an order (allocation/machine load, request, operations change or pledge, MRP creation of splits), the program checks whether the integration is active and, if it is active, it executes the delivery of registration for PC-Factory. If there is no error, the register does not display any message. In case of error, a message is displayed and a delivery pendency can be created in program PCPA110. At the end of the process, the routines processing multiple orders, for example machine load, the amount of records that were sent to PPI-Multitask is displayed and the ones which had delivery pendency. Note: Some routines generate pendencies without executing the questioning due to the number of processed orders.
  Routines affected by integration: Maintenance of Orders (MATA650), Routine to Establish Orders (MATA651), Maintenance of Operations (MATA632 or MATA637), Maintenance of Allocation (MATA380 and MATA381), Machine Load (MATA690) amd MRP (MATA712), Production splits (SFCA310).
• Program of PCPA110 pendencies management - this program aims at managing pendencies/exceptions related to integration that are created when the message was not sent to PC-Factory, whether they are pendencies or errors. Enables the reprocessing of a message, deletion of a pendency and the XML view, besides having the filter per date of delivery, transaction, type of pendency and generating routine. The routine also enables to query the messages successfully sent.
• Synchronization program PCPA111 - enables the deliver of information from product, stock location, resource, tools, script, structure, address, balance in stock and production order, it aims at updating the PC Factory database. Besides filters defined in PCPA109, you can also add new filters for each table.
• Production Annotation: This routine consists in WebService to receive annotation of production executed by PC-Factory. You can also process production annotation and resource stoppage. Executes the same process the routines MATA681 and MATA682. When the Shop Floor is installed, it runs the same process the routine SFCA316 and SFCA311.
  The integration flow is the following: a. the Operator normally reports according to its operation in PCFactory b. In a batch or triggered process, parallel to the system, the message is assembled (XML) according to Schema of Single Message TOTVS and the delivery of message (XML) for Protheus, validating the message and follow the respective business adapter up  (MATA681/MATA682 or SFCA316/SFCA311) for processing. c. In case of mistakes, this report has pending status for delivery in the MES software and the user take actions in PC-FActory (Protheus does not keep traceability of receipt messages, but it registeres in LOG the processing). d. In case of success in report, the number of the report record executed in Protheus returns to PC-Factory. This number can be used in case of reversal.
• UPdate of balance in PC-Factory will happen as follows:
  a. Request: the PC-Factory requests balance generating request XML message. In this message, you can request balance per item, per stock location, among others.
  b. Protheus Updating: When balance is updated, Protheus must send a XML message to PC-Factory. The main routines of ERP as inbound and sales inbound, some internal movements and addition of balance through MATA220 and MATA805 are considered.
• Stock movements: When PC-Factory performs stock movements and transfers, these movements are updated in Protheus.
  In case of movements, if I (input), it must run MATA250. If O (output), it must run MATA240. In case of transfers, it runs MATA261.
• Refusal/annotation of loss. This routine consists in WebService to receive the refusal records in PC-Factory. The same process is executed in MATA685 routines.
• Query of Import Log PCPA112: This routine consists in the query of annotation records that were processed by the integration Protheus x PC-Factory. Routine must display the annotation executed and the status of each process.

Entry Point

To make the use of integration easier and flexible in any productive environment, some entry points were created to solve possible specific situations not answered by the default process and also to enable more precise configurations in the integration use:

Annotation: The entry point MATI681CRG enables to add information that is used in annotation of production and in the stoppage annotation, table SH6. Example: In case there is a specific field or table not handled by the integration, you can use this function to set its content. Details in: MATI681CRG_Add_information_Adapter_of_annotation.

Annotation: The entry point  MT680VAL  enables to validate if any information must be mandatory as time, quantity, among others. These validations are under the customers' responsibility, as each has its own rule. Details in: MT680VAL - Addition of Productions.

Annotation: The entry point MATI680OPR enables to change the code of operation received in the annotation of production. Details in: MATI681OPR_Edit_operation_code_message_annotation_production.

Annotation: The entry point MTI681QTAP enables to edit the quantity received in the annotation of production. This entry point is indicated to apply the conversion factor in the amount of annotation when ERP and PC-Factory work with different unit of measurement. Details in: MTI681QTAP_Edit_amount_of_annotation_ProductionAppointment.

Annotation: The entry point MATI681EXC enables to check whether the annotation is executed. This entry point is indicated for validations that hinder the annotation of production and stoppage. It is also used for cases in which you have to update some information before annotation (example: reversal an address). Details in: MATI681EXC_Processes_Message_Annotation.

Production Order: The Entry Point  MTI650ADOP enables to add a new operation in the production orders message. For each operation being sent   this entry point is executed once. Details in:: MTI650ADOP_Add new operation of production order adapter.

Production Order: Production Order: The Entry Point MTI650FCOP enables to change the second unit of measure of the operation being sent in the production orders message. Details in:: MTI650FCOP_Change_conversion_factor_second_unit_of_operation_measure_adapter_production_order.

Production Order: The Entry Point MTI650QTOP enables to change the amount of operation being sent in the production orders message. Details in: MTI650QTOP_Change_quantity_of_operation_adapter_production_order.

Production Order: The Entry Point MTI650UMOP enables to change the second unit of measure of the operation being sent in the production orders message. Details in: MTI650UMOP_Change_second_unit_of_measure_of_operation_adapter_productionn_order.

Production Order: The Entry Point MTI650TMAC enables to change the machine time (TimeMachine) in the message of ProductionOrder. Details in: MTI650TMAC_Edit_amount_of_machine_time_production_order.

Production Order: The Entry Point MTI650LOTE enables to generate the Batch of the order in the tag LotCode in the message ProductionOrder. Details in: MTI650LOTE_Add_batch_in_message_of_production_orders

Registers: The Entry Point PCPXFUNPPI  enables to inhibit the integration in certain routine. Example: If you do not want integration to occur in the creation of MATA650 orders, you can use this function to inhibit the use. Details in: PCPXFUNPPI_Routines_not_executing_integration_with_the_PC_Factory.

Register of Item: The Entry Point PCPADDTAGS enables to add specific tags in TOTVS standard messages. It is enabled for the registration of the item MATA010. Details in: PCPADDTAGS_Add_information_XML_integration_TOTVS_MES.

Register of Processes: The Entry Point PCPADDTAGS enables to add specific tags in TOTVS standar messages. It is enabled for the registration of script MATA632. Details in: PCPADDTAGS_Add_information_XML_integration_TOTVS_MES

Internal Movements. The entry points MATI250CRG and MATI240CRG enable specific validation. These validations are under the customers' responsibility, as each has its own rule. You cannot generate the values of fields that were generated by message. Details in:MATI240CRG_Add_information_Adapter_of_internal_movements and MATI250CRG_Add_information_Adapter_of_production_movements

Transfers: The entry point MI261RCV does not enable the execution of the integration. Details in: MI261RCV_Execute_integration_TransferWarehouse

Refusal: The Entry Point MATI685EXC enables to check whether the refusal is executed. This entry point is indicated for the validations hindering the annotation of refusal or updating of information necessary to execute the refusal. Details in: MATI685EXC_Processes_Message_Refusal

Execute in various branches

In an environment with various branches, just one WEBSERVICE is necessary for execution. The TAGs indicate the branch in which the annotation is processes:

<CompanyId>10</CompanyId>

<BranchId>CLSC0001</BranchId>

Note: When these tags are in blank the system considers what is defined in APPSERVER.ini in session WEBSERVICE field PrepareIn.

[WebServices]

PrepareIn=99,01

Control of latency

There are situations in which the webservice waiting time is lower than the time of processing of information to ERP. There may be situations in which the ERP continues to process the import and the WebService of PC-Factory stops waiting for the answer. When PC-Factory does not receive the answer in time, the same file is resent, generating then duplicity in the message processing.

Solution:

Control ID of PC-Factory for received messages. Every received message must be handled like this:

• ProductionAppointment
• StopReport
• MovementsInternal
• TransferWarehouse
• StopReason
• WasteReason

In the XML´s, the TAG  Key name = "IDPCfactory" is used.

<BusinessEvent>

      <Entity>Entity</Entity>

      <Event>upsert</Event>

      <Identification>

        <key name="IDPCFactory">29892829</key>

      </Identification>

</BusinessEvent>

The return with error displays a message with the following pattern:

<ProcessedOn>2017-03-28T09:11:17</ProcessedOn>

   <Status>ERROR</Status>

   <ListOfMessages>

      <Message type="ERROR" code="N">MENSAGEM</Message>

   </ListOfMessages>

</ProcessingInformation>

The return XML must follow this rule:

• When ID is processed and has ERROR

              Retorns the ID PC-Factory in tag  <UUID>

              In the tag Message type="ERROR" code="2", uses the 2 to indicate error.

              The message is: ID xxxx already processed. Status: error message”.

             Example: <Message type="ERROR" code="2">ID productionappointment-0038 already processed. Status: ProductionOrderNumber not registered in Protheus.</Message>

• When ID is already successfully processed

              Retorns the ID PC-Factory in the tag  <UUID>

              In the tag Message type="ERROR" code="3", uses the 3 to indicate the successfull processing.

             The message is: "ID xxxx already processed. Status: ID of Protheus" or  "ID xxxx already processed. Status: Reprocessed. ID of Protheus" when PC-Factory sends more than once.

             Example 1:      <Message type="ERROR" code="3">ID productionappointment-0038 already processed. Status: 5091</Message>

             Example 2:      <Message type="ERROR" code="3">ID productionappointment-0038 already processed. Status: Reprocessed. 5091</Message>.

• When ID already is in base but in processing

              Retorns the ID PC-Factory in the tag  <UUID>

              In the tag Message type="ERROR" code="4", uses the 4 to indicate that is in processing.

              The message is: ID xxxx is being processed by Protheus.

              Example: <Message type="ERROR" code="4">ID apapapapeaaa is being processed by Protheus.</Message>

Note:

The return, when message is processed "right away" , within the waiting time of the webservice, is "1" - Processed for the first time with ERROR or OK.

Example:

With Error:

<ProcessingInformation>

   <ProcessedOn>2017-03-28T09:00:03</ProcessedOn>

   <Status>ERROR</Status>

   <ListOfMessages>

      <Message type="ERROR" code="1">ProductionOrderNumber not registered in protheus.</Message>

   </ListOfMessages>

</ProcessingInformation>

Successfully:

<ProcessingInformation>

         <ProcessedOn>2017-03-28T08:57:28</ProcessedOn>

         <Status>OK</Status>

</ProcessingInformation>

<ReturnContent>

         <ListOfInternalId>

            <InternalId>

               <Name>PRODUCTIONAPPOINTMENTINTERNALID</Name>

               <Destination>5090</Destination>

            </InternalId>

         </ListOfInternalId>

</ReturnContent>

Unexpected situations may occur: the stoppage of Protheus service, downsizing of database, power outage, among others. If during the integration processing, the record of PC-Factory (ID of PC-Factory) may be locked up and there is no output of message from the processing queue. To handle this situation:

The PC-Factory tries to send by determination of time - time which is parameterized in PC-Factory. If you continue to receive the same message after the parameterized time, PC-Factory generates pendency of delivery and moves to the next record. Upon doing this, a counter of messages that were not sent is generated. When this counter reaches a (parameterized) limit, the integration process is stopped so the users can solve the problem. The processing control is registered in LOG SOH table.

Check below, table of sent codes:

Important:

• If a record gets locked with status "record being processed", it can be unlocked by routine PCPA112, including the corresponding IDMES.
• The reprocessing of a message with ERROR(2) can be done passing the tag Reprocess = true.
  Example:

<BusinessEvent>

            <Entity>productionappointment</Entity>

            <Event>upsert</Event>

            <Identification>

              <key name="IDPCFactory">9o93049u88557</key>

              <key name="Reprocess">true</key>

            </Identification>

        </BusinessEvent>

Routines

Parameterization - PCPA109

Setting parameters directly influences records not moved between the two systems.

The parameter settings routine has the following fields:

• Active: It indicates whether the integration is active. When you select this field, the others are disabled. If this field is not marked, you cannot perform any other action in the routine.
• Path: It indicates the path of the PC-Factory WebService. After the path, there is a test button to check if the webservice is active.
• It has a XML panel.
  This panel indicates:
  - Generate XML - By selecting this field, it generates the XML of exchanged messages, If you do not select it, the system saves it only in tables. You are not required to create files. Use it as a tool to find problems. The content sent is always based on what is registered in the table.
  - Sent - Directory where XMLs sent to PC-Factory are saved
  - Pending - Directory where XMLs not sent PC-Factory are saved
  The name of the files follows the standard below:
  OK_<MSG>_<DATAHORA>_<REGISTRO>
  PEND_<MSG>_<DATAHORA>_<REGISTRO>
  ERR_<MSG>_<DATAHORA>_<REGISTRO>
  Where: OK - Message sent with no problems
             PEND- Message not sent
             ERR - Message sent, but returned with error.
             MSG - Name of message. Ex.: Item, Wharehouse, Workcenter, etc.
             DATETIME: Date and Time of sending
             RECORD: Record code being sent. Ex.: Item code, order number, etc.
  Note: If you select Generate XML, you must enter the directories.

Each file transacted has a folder. For each folder, you can assemble filters. These filters are used in routines that send PC-Factory information enabling you to select what must be sent. The fields of selected table (folders) and operators are displayed so filters are assembled. Like the filters, some files are parameterized.

The routine has the following folders:

• Product
• Stock Location
• Resource
• Machine 
  The machine folder is only displayed when shop floor is in use.
• Tool
• Production Order
  
  MRP Panel: Indicates how the system must behave in relation to the orders generated by MRP. It will have the following options:
  "Does not integrate": The orders generated by MRP are not sent to PC-Factory by the MRP calculation.
  "Generate Pendency": The orders generated by MRP are registered in the pendencies of delivery
  "Integrates": The orders generated by MRP are sent to PC-Factory by the MRP calculation.
  
  
  For production order folder, a field to determine how the consumption of components in the panel "Consumption of Components". This field may have the following values:

"1" - BackFlush: Whenever issue of components is executed according to what is defined in Engineering.   

"2" - Actual Consumption: Consumption according to component list.Painel "Operações": Define se o filtro criado no folder "Roteiros" deve ser utilizado para filtrar as operações da ordem de produção.     

"Scrap" Panel: Defines the location of stock/deposit for the scrapped item when scrap is the same product of the production order. When the deposit - "WharehouseCodeTo" is in blank, in the message ProductionAppointment, use what was defined in the parameter.

• Scripts
• Structure
• Address
• Movimentos e transferência
  Os movimentos de estoque, entrada ou saída e também as transferências são arquivos recebidos pelo Protheus. Não necessita de filtros, porém deverão ser criados alguns parâmetros para o processamento. São eles:
  Type of Input Movement: Use field SOE.OE_VAR1
  Type of Output Movement: Use field SOE.OE_VAR2
  These types of movements are registered in MATA230
• Stock balance
  For Stock balance folder, the option has three filters. Table SB2, SB8 and SBF.  
  It can also indicate in which process of movement, balance is sent to PC-Factory
  Where: 
  Inbound Invoice: SOE.OE_VAR1 (Marked = 1; Unmarked = 0 )
  Sale Invoice     : SOE.OE_VAR2 (Marked = 1; Unmarked = 0 )
  Internal movements: SOE.PARINTG (Marked = 1; Unmarked = 0 )
  Balance Implementation: SOE_OE_VAR3(Marked = 1; Unmarked = 0 )
  These options are valid only for sending from Protheus to PC-Factory. For request (request of PC-Factory) will not have filters.

Synchronization - PCPA111

The synchronization is the process that is used to populate or update the base of PC-Factory with data from Protheus. It will work the same manner the other routines of integration do, by integrating a XML message to WebService of PC-Factory, following the parameterizations defined in PCPA109. The only difference is that all data of the table being integrated are viewed (following the filters) instead of only one record.

Pendencies - PCPA110

Routine to resend messages not sent to PC-Factory system, whether they are pendencies or mistakes. The routine also enables to query the messages sent (delivery LOG).

To check pendencies and log of messages moved between the systems:

• Structure Register
• Product/Item
• Location of Stock (deposits)
• Resource PCP
• Production orders (Operations, Scripts, Components, Splits) 
• Shop floor resources - Tools, Team and Operator
• Tools
• Shop Floor Machinery
• Scripts - Operations
• Addresses
• Balance 

With the following options: 

• Reprocess: 
  For each line selected, the messages must be sent.
• Delete
  Delete selected records
• Save XML
  This option enables to save the XML in a directory location of the machine that is processing the pendencies routine.
• Update
  Redo the search of records, updating data on screen

Import Log - PCPA112

When receiving data from PC-Factory, Webservice Protheus saves information so they are queried (SOG table). Find the list of movements generation LOG below:

• Production annotation
• Stoppage annotation
• Scrap Reason
• Stoppage Reason
• Stock movements
• Transfer

Messages

Registers

Transaction Item: Item_3_001.xsd
Message Identifier: Item
Version: 3_001
Protheus Module: SiGAPCP
Sending Type: Synchronous

Deposit Transaction: Warehouse_1_001.xsd
Message Identifier: Warehouse
Version: 1_001
Protheus Module: SiGAPCP
Sending Type: Synchronous

Transaction Resource PCP / Machine SFC: Machine_1_000.xsd
Message Identifier: Machine
Version: 1_000
Protheus Module: SIGAPCP, SIGASFC
Sending Type: Synchronous

In PCP, the machines are registered in the routine of resources MATA610 and in the Shop Floor, the routine is SFCA002. Nomenclature is also changed. When using Shop Floor, it is named MACHINE. When using only PCP. it is RESOURCE. The routine of parameters PCPA109 is ready to present the name according to the use of the system.

SFC Resource Transaction: Resource_1_000
Message Identifier: Resource
Version: 1_000
Protheus Module: SIGAPCP
Sending Type: Synchronous

Transaction Structure: ItemStructure_1_000.xsd 
Message Identifier: ItemStructure
Version: 1_000
Protheus Module: SiGAPCP
Sending Type: Synchronous

Message	Tag	Description	Table/Field: Protheus	Type	Table/Field: PC-Factory	Type
BusinessContentType	CompanyId	Company Code		CHAR(02)
	CompanyInternalId	Company+Branch	COMPANY + SG1.G1_BRANCH
	ItemInternalId	Company+Branch+code parent item	COMPANY + SG1.G1_BRANCH + SG1.G1_COD
	ItemCode	Code parent item	SG1.G1_COD	CHAR(15)	TBLInWOHD.ProductCode TBLInWOHD.WOCode	CHAR(30)
	ItemAmount	Base quantity of parent item	SB1.B1_QB	NUM(07)	TBLInWOHD.TotalQTY	DEC(19,4)
ItemComponentType
	ItemSequence	Sequence of component	SG1.G1_TRT	NUM(05)	TBLInBillMat.BillMatExtCode	CHAR(20)
	ItemComponentCode	Code item component	SG1.G1_COMP	CHAR(15)	TBLInBillMat.ProductCode	CHAR(20)
	ItemComponentInternalId	Internal Id of Item Component	COMPANY + SG1.G1_BRANCH + SG1.G1_COMP
	InitialDate	Validity Initial Date	SG1.G1_INI	DATE	TBLInWOHD.DtPlanStart	DATETIME
	FinalDate	Validity End Date	SG1.G1_FIM	DATE	TBLInWOHD.DtPlanEnd	DATETIME
	IsGhostMaterial	Indicates whether it is ghost	SB1.B1_FANTASM	BOOLEAN ( FALSE ou TRUE)
	ItemComponentAmount	Quantity of component item	SG1.G1_QUANT	DEC(12,6)
	LossFactor	Factor of loss	SG1.G1_LOSS	DEC(05,2)
ListOfScript
	Scriptcode	Code of Script	SGF.GF_SCRIPT	CHAR(02)	TBLInWOHD.ExtCode	CHAR(20)
	ScriptAlternative	Alternative of Script	--
	ActivityIntenalID	ID Operation	--
	ActivityCode	Code of Operation	SGF.GF_OPERAC	CHAR(02)	TBLInWodet.Code	CHAR(10)
	ActivityComponentSequence	Sequence of component in the operation	SGF.GF_TRT	NUM(03)

Script Transaction - Item Operations: ItemScript_1_000.xsd 
Message Identifier: ItemScript
Version: 1_000
Protheus Module: SiGAPCP
Sending Type: Synchronous

Addresses Transaction: AdressStock_1_000.xsd
Message Idenfier: AdressStock
Version: 1_000
Protheus Module: SiGAPCP
Sending Type: Synchronous

Balance Transaction: ItemStockLevel_1_000.xsd
Message Identifier: ItemStockLevel
Version: 1_000
Protheus Module: Various
Sending Type: Synchronous

QuantityUpdated

Waste Reason Transaction: WasteReason_1_000.xsd 

Message Identifier: WasteReason
Version: 1_000
Protheus Module: SIGAPCP/SIGASFC
Sending Type: Synchronous

Stop Reason Transaction: StopReason_1_000.xsd

Message Identifier: StopReason
Version: 1_000
Protheus Module: SIGAPCP/SIGASFC
Sending Type: Synchronous

Production Order Transaction: ProductionOrder_2_004.xsd

Message Identifier: ProductionOrder
Version: 2_003
Module Protheus: SIGAPCP
Sending Type: Synchronous

Message	Tag	Description	Table/Field	Type	Table/Field: PC-Factory	Type
BusinessContentType	Number	Number Production Order	SC2.C2_NUM + SC2.C2_ITEM + SC2.C2_SEQUEN	CHAR(20)	TBLInWOHD.Code	CHAR(41)
	ProductionOrderUniqueID	Company+Branch+Production Order	COMPANY + SC2.C2_BRANCH + SC2.C2_NUM + SC2.C2_ITEM + SC2.C2_SEQUEN	CHAR(30)
	ItemCode	Code Item	SC2.C2_PRODUCT	CHAR(15)	TBLInWOHD.ProductCode	CHAR(20)
	ItemDescription	Description Item	SB1.B1_DESC	CHAR(40)
	Type	Type of Order	1= Internal; 2=External; 3=Internal/External; 4=Rework; 5=Fixing; 6=Maintenance; 7=Fixed Asset; 8=Tooling; 9=Reuse	CHAR(01)	TBLInWOHD.WoTypeCode	CHAR(20)
	Quantity	Quantity	SC2.C2_QUANT	DEC(12,2)	TBLInWOHD.TotalQty	DEC(19,4)
	ReportQuantity	Quantity Reported	SC2.C2QUJE	DEC(12,2)
	UnitOfMeasureCode	Unit of Measure	SC2.C2_UM	CHAR(02)	TBLInWoDet.Unit1Code	CHAR(05)
	RequestOrderCode	Request Code Production Order	SC2.C2_ORDER	CHAR(06)
	StatusOrderType	Order Status	Estimated/Opened = 1 Started = 6 Partial/Total Closed = 7 Idle = 9	CHAR(01)	TBLInWOHD.Status	SMALLINT
	WarehouseCode	Code Deposit	SC2.C2_LOCAL	CHAR(02)	TBLInWOHD.AuxCode1	CHAR(20)
	EndOrderDateTime	End Date Production Order CP	SC2.C2_DATPRF	DATE	TBLInWOHD.DtPlanEnd	DATETIME
	StartOrderDateTime	Start Date Production Order CP	SC2.C2_DATPRI	DATE	TBLInWOHD.DtPlanStart	DATETIME
	AbbreviationProviderName	Name Customer	SC5.C5_CLIENTE ( SA1.A1_NOME)	CHAR(30)
	ScriptCode	Code Script	SC2.C2_SCRIPT	CHAR(02)
	ReportOrderType	Type of Report	1 = Order; 2 = Operations; 3 = Control Point; 4 = Item	CHAR(01)
ListOfActivityOrders
	ProductionOrderNumber	Production Order	SC2.C2_NUM + SC2.C2_ITEM + SC2.C2_SEQUEN	CHAR(20)	TBLInWoDet.Wocode	CHAR(10)
	ActivityID	ID of Record	RECNO (SG2,SHY ou SH8)	CHAR(10)
	ActivityCode	Code Operation	SG2.G2_OPERAC SHY.HY_OPERAC SH8.H8_OPER	CHAR(02)	TBLInWoDet.WODetCode+Split	CHAR(10)
	ActivityDescription	Description Operation	SG2.G2_DESCRI	CHAR(40)	TBLInWoDet.WODetName	CHAR(30)
	Split	Split of operation	SH8.H8_DESDOBR	CHAR(04)
	ItemCode	Code of item	SC2.C2_PRODUCT	CHAR(15)
	ItemDescription	Description of item	SB1.B1_DESC	CHAR(40)
	ActivityType	Type Operation	1 - Register ; 2-Does not register	CHAR(01)
	WorkCenterCode	Code Work Center	SG2.G2_CTRAB SHY.HY_CTRAB SH8.H8_CTRAB	CHAR(06)	TLBInWODet.ManagerGrpCode	CHAR(15)
	WorkCenterDescription	Description Work Center	SHB.HB_NOME	CHAR(30)
	UnitTimeType	Type Unit Time	1 - Hours; 2 - Minutes; 3- Seconds; 4 - Days	CHAR(01)	TLBInWODet.StdSpeedFormat	TINYINT
	TimeResource	Time Resource (Standard time for lot)	SG2.G2_TEMPAD	DEC(05,2)	TLBInWODet.StdSpeed	DEC(28,23)
	TimeMachine	Time Machine (Time to order)	SG2.G2_TEMPAD * SC2.C2_QUANT SHY.HY_TIME  SH8.H8_HRINI - SH8.H8_HRFIM	DEC(14,4)	TLBInWODet.StdSpeed	DEC(28,23)
	TimeSetup	Tiem Setup	SG2.G2_SETUP SHY.HY_TIMES SH8.H8_SETUP	DEC(15,4)	TLBInWODet.SetUpTime	INT
	TimeMOD	Time Man	--
	TimeIndMES	Iindicator of time in MES	1 = Machine Time; 2 = Labor Time; 3 = Choice by MES.	CHAR(01)
	ScriptCode	Code Script	SG2.G2_CODE SHY.HY_SCRIPT SH8.H8_SCRIPT	CHAR(02)
	LaborCode	Code Direct Labor	MOD+CC	CHAR(08)
	UnitItemNumber	Standard Lot	SG2.G2_LOTEPAD	NUM(05)	TLBInWODet.StdSpeed	DEC(28,23)
	IsActivityEnd	Last Operation	In the last operation, TRUE. Otherwise, FALSE.	BOOLEAN	TLBInWODet.ReportTrigger	TINYINT
	MachineCode	Machine Code	SG2_RESOURCE SHY_RESOURCE H8_RESOURCE	CHAR(06)
	StartPlanDateTime	Date/Time Start Schedule	SHY.HY_HORAINI SC2.C2_DATPRI SH8.H8_DTINI	DATE	TLBInWODet.StartPlanDateTime	DATETIME
	EndPlanDateTime	Date/Time End Schedule	SHY.HY_HORAFIM SC2.C2_DATPRF SH8.H8_DTFIM	DATE	TLBInWODet.EndPlanDateTime	DATETIME
	ProductionQuantity	Quantity to produce in operation	SHY.HY_QUANT  SH8.H8_QUANT  SC2.C2_QUANT	DEC(12,2)	TLBInWODet.Qty	DEC(19,4)
	ActivityQuantity	Quantity of operation	SHY.HY_QUANT  SH8.H8_QUANT  SC2.C2_QUANT	DEC(12,2)
	UnitActivityCode	Unit of measure	SB1.B1_UM	CHAR(02)	TLBInWODet.Unit1Code	CHAR(5)
	SecondUnitActivityCode	Second unit of measure in operation	--		TLBInWODet.Unit2Code	CHAR(5)
	SecondUnitActivityFactor	Conversor Factor for second unit in operation	--		TLBInWODet.Unit2Factor	DEC(8,4)
	ResourceQuantity	Quantity of resources	SG2.G2_MAOOBRA SHY.HY_MAOOBRA	NUM(03)
ListOfMaterialOrders
	ProductionOrderNumber	Production Order	SC2.C2_NUM + SC2.C2_ITEM + SC2.C2_SEQUEN	CHAR(20)	TBLInBillMat.Wocode	CHAR(41)
	MaterialID	ID of reservation record	SD4.R_E_C_N_O_	CHAR(10)
	MaterialCode	Code Reservation Item	SD4.D4_COD	CHAR(15)	TBLInBillMat.ProductCode	CHAR(20)
	MaterialDescription	Description of Item	SB1.B1_DESC	CHAR(40)
	ScriptCode	Code Script	SD4.D4_SCRIPT	CHAR(02)
	ActivityCode	Code Operation	SD4.D4_OPERAC	CHAR(02)	TBLInBillMat.WODetCode	CHAR(10)
	WarehouseCode	Code Deposit	SD4.D4_LOCAL	CHAR(02)	TBLInBillMat.ExtCode	CHAR(20)
	MaterialDate	Date Reservation	SD4.D4_DATE	DATE
	MaterialQuantity	Quantity of Reservation	SD4.D4_QUANT	DEC(12,2)	TBLInBillMat.TotalQty	DEC(19,4)
	LotCode	Lot	SD4.D4_LOTECTL	CHAR(10)
	PertMaterialNumber	Sequence of item	SD4.D4_TRT	CHAR(03)
	RequestType	Type of Request	SB1.B1_APROPRI	CHAR(01)	TBLInBillMat.Comments	CHAR(500)
ListOfAllocatedMaterial
	WarehouseCode	Code Deposit	SD4.D4_LOCAL	CHAR(02)	TBLInMovMat.WarehouseCode	CHAR(15)
	LotCode	Code Lot	SD4.D4_LOTECTL SDC.DC_LOTECTL	CHAR(10)	TBLInMovMat.LotCode	CHAR(41)
	LocationCode	Location/Address	SDC.DC_LOCALIZ	CHAR(15)	TBLInMovMat.AddressCode	CHAR(15)
	ActivityCode	Code Operation	SD4.D4_OPERAC	CHAR(02)	TBLInMovMat.WoDetCode	CHAR(10)
	ScriptCode	Code Script	SD4.D4_SCRIPT	CHAR(02)
	AllocationQuantity	Allocated Quantity	SD4.D4_QUANT  SDC.DC_QUANT	DEC(12,2)	TBLInMovMat.Qty	DEC(19,4)
	AllocationType	Type Allocation	1 = Adds;2=Decreases;3=Absolute Value	CHAR(01)	TBLInMovMat.AllocationType	INT
	SubLoteCode	Sub Lot	SD4.D4_NUMLOTE SDC.DC_NUMLOTE	CHAR(06)
	NumberSeries	Number of Series	SDC.DC_NUMSERI	CHAR(20)
	LotDueDate	Validity Date	SD4.D4_DTVALID	DATE	TBLInMovMat.LotDtValidity	DATETIME
ListOfQuotaActivity
	ProductionOrderNumber	Number Production Order	CY9.CY9_NRORPO	CHAR(20)
	ControlType	Selection Split	--
	ActivityID	ID Operation	CY9.CY9_CDAT	CHAR(10)
	ItemCode	Code of item	CYY.CYY_CDAC	CHAR(15)
	ItemDescription	Description of item	CYY.CYY_DSAC	CHAR(40)
	StartActivityDateTime	Date/Time Start Activity	CYY.CYY_DTBGAT / CYY.CYY_HRBGAT	DATETIME	TBLInWODet.StartPlanDateTime	DATETIME
	EndActivityDateTime	Date/Time End Activity	CYY.CYY_DTEDAT / CYY.CYY_HREDAT	DATETIME	TBLInWODet.EndPlanDateTime	DATETIME
	ApprovedQuantity	Approved Quantity	CYY.CYY_QTATAP	DEC(13,4)
	ScrapQuantity	Scrapped Quantity	CYY.CYY_QTATRF	DEC(13,4)
	MachineCode	Code Machine	CYY.CYY_CDMQ	CHAR(20)	TBLInWODet.ResourceCode	CHAR(15)
	MachineDescription	Description of Machine	CYY.CYY_DSMQ	CHAR(40)
	ActivityQuantity	Estimated Quantity	CYY.CYY_QTAT	DEC(12,4)	TBLInWODet.QTY	DEC(19,4)
	StandardSetup	Standard Time Preparation	CYY.CYY_QTPASU	NUM(10)
	StandardActivity	Standard Time Operation	CYY.CYY_QTPAAT	NUM(10)
	StandardPostprocessing	Standard Time Post_process	CYY.CYY_QTPAPP	NUM(10)
	StandardMachine	Standard Time Machine	CYY.CYY_QTPAMQ	NUM(10)
	StandardOperator	Standard Time MOD	CYY.CYY_QTPAOE	NUM(10)
	UsedCapacity	Capacity Used	CYY.CYY_QTVMAT	DEC(12,4)
	ActivityTimeQuantity	Activity Available Time	CYY.CYY_HRDI	CHAR(08)
	ReportQuantity	Reported Quantity	CYY.CYY_QTATRP	DEC(13,4)
	ReworkQuantity	Reworked Quantity	CYY.CYY_QTATRT	DEC(12,4)
	StartSetupDateTime	Date/Time Start Setup	CYY.CYY_DTBGSU / CYY.CYY_HRBGSU	DATETIME
	EndSetupDateTime	Date/Time End Setup	CYY.CYY_DTEDSU / CYY.CYY_HREDSU	DATETIME
	TimeSetup	Time Setup	CY9.CY9_QTTESU	NUM(10)	TBLInWODet.SetUpTime	TINYINT
	TimeMachine	Machine Time	CY9.CY9_QTTEMQ	NUM(10)	TBLInWODet.StdSpeed	DEC(28,23)
	TimeOperator	Time MOD	CY9.CY9_QTTERC	NUM(10)
	TimePostprocessing	Post Process Time	CY9.CY9_QTTEPP	NUM(10)
	QuotaActivityID	ID Split	CYY.CYY_IDATQO	CHAR(05)	ActivityCode+ TBLInWODet.WODetCode	CHAR(10)
	WorkCenterCode	Work Center	CY9.CY9_CDCETR	CHAR(10)	TBLInWODet.ManagerGrpCode	CHAR(15)
	ReportedSplit	Reported Split	CYY.CYY_LGQORP	BOOELAN
	StatusActivityType	State Operation	CYY.CYY_TPSTAT	CHAR(01)
ListOfQuotaActivityTools
	ToolCode	Tool	CYY.CYY_CDFE	CHAR(20)
	ToolQuantity	Quantity Tool	CYY.CYY_QTFE	NUM(03)

Processes

Production Annotation Transaction: ProductionAppointment_2_000.xsd
Message Identifier: ProductionAppointment
Version: 2_003
Protheus Module: SIGAPCP/SIGASFC
Sending Type: Synchronous 

Consumption notes of components:

• The consumption of components must follow the parameterization of PCPA109. In parameters routine is defined how the treatment of components consumption:
  1 - BackFlush: Whenever issue of components is executed according to what is defined in Engineering. Disregard the list of consumption SupplyOrder.
  2 - Actual Consumption: It consumes according to the list of components SupplyOrder sent in message.
• In the consumption of components, the process must follow this rule, according to parameterization:
  If parameter MV_REQAUT is 'D' the DIRECT materials are entered and the INDIRECT are automatically loaded. To load the Indirects the type of movement must have field Ind Approp as O in routine MATA230.
  If parameter MV_REQAUT is 'A', the consumption of materials is executed for all components.
• It must consider the movement type of register of parameters PCPA109, folder MOVEMENTS. If input, use field OE_VAR1. If output, use field OE_VAR2. When Shop Floor is used, it must use movements parameterized in SIGASFC (MV_SFRQMB and MV_TMPAD).
• Quando consumo real, deverá considerar o tipo de movimento do cadastro de parâmetros PCPA109, folder "Movimentos e Transferência". Para saídas usar o campo OE_VAR2. Quando usa o Chão de Fábrica, deverá usar as movimentações parametrizadas no SIGASFC (MV_SFRQMB).
• For the annotation, the type of movement is the one in the parameter MV_TMPAD, for SIGAPCP and SIGASFC.
  When back-flush, it uses the types of standard movements of the routine.
• In PC Factory, batch and number of series are not used at the same time. The return of this content is through tag SupplyOrder - LotCode, which can be the Lot or number of series, according to register of item.

Shop Floor Notes

• Quantity reported  CYV_QTATRP, sum of quantity approved and rejected.
• Start and End Date/Time and code of Preparation despite being virtual, if machine demands setup (CYB_LGUSU) must send tags SetupCode, StartSetupDateTime and EndSetupDateTime.
• If document, tag DocumentCode, is blank, the production order number is saved.
• The fields Reservation Date 'CZP_DTMT' must receive the content of table CYP.CYP_DTMT 
  The reservation quantity 'CZP_QTMT' must receive the content of table  CYP.CYP_QTMT
  State 'CZP_TPST' must receive content of table CYP.CYP_TPST 
• The operation unit time, CZ0_QTTEUN, must be generated according to rule SFCA314

Scrap Notes

• Register scrap reason (tags of ListOfWasteAppointments), updating data from table SBC
• If reason of scrap is not registered, it is added to reasons register of table SX5. 
  Where:  
  Code of reason is X5_CHAVE
  Table of reason is '44'. 
  For Shop Floor, table - CY0 must be generated.
• Scrap reasons have different sizes in tables. Validate it if receipt code does not exceed the size of columns in Protheus.
  When it uses the PCP it must validate a SX5.X5_CHAVE and SBC.BC_MOTIVO.
  When it uses the SIGASFC validate against the CYO.CYO_CDRF, CY0.CY0_CDRF and SBC.BC_MOTIVO.

Machine Stoppage Annotation Transaction: StopReport_1_001.xsd StopReport_1_001.xsd

Message Identifier: StopReport
Version: 1_001
Protheus Module: SIGAPCP
Sending Type: Synchronous

Transaction Balance in Stock - Request: StockLevel_2_000.xsd
Message Identifier: StockLevel
Version: 2_000
Protheus Module: SIGAPCP
Sending Type: Synchronous

For this type of updating the PC Factory requests balance to Protheus. Message has two parts. Request, in which parameters for balance query and the Return, which has the balance return, are displayed.

This Request is generated by PC-Factory and sent to Protheus. This Return is generated by Protheus to PC-Factory.

Request

Return

Message	Tag	Description	Table/Field	Type
ReturnContentType	ClosingStockDate	Stock closing date	--
ListOfReturnItem	CompanyId	Company
	BranchId	Branch
	CompanyInternalId	Company + Branch
	ItemInternalId	Code of product	SB2.B2_COD	CHAR(15)
	ReferenceCode	Reference	--
ListOfStockBalance
	WarehouseInternalId	Location of Stock (Warehouse/Deposit)	SB2.B2_LOCAL	CHAR(10)
	LotNumber	Number of Lot	SB8.B8_LOTECTL	CHAR(10)
	SubLotCode	Sub Lot	SB8.B8_NUMLOTE	CHAR(10)
	LotExpirationDate	Validity Date	SB8.B8_DTVALID	DATE
	SerialNumber	Number of series	SBF.BF_NUMSERI	CHAR(20)
	Address	Location	SBF.BF_LOCALIZ	CHAR(15)
	CurrentStockAmount	Balance of Product in quantity	SB2.B2_QATU SB8.B8_BALANCE SBF.BF_QUANT	DEC(17,4)
	BookedStockAmount	Quantity reserved in Stock	SB2.B2_RESERVATION SB8.B8_ALLOCATION SBF.BF_ALLOCATION	DEC(17,4)
	AvailableStockAmount	Balance available of Product in quantity	SB2.B2_QATU - SB2.B2_RESERVATION SB8.B8_SALDO - SB8.B8_ALLOCATION SBF.BF_QUANT - SBF.BF_ALLOCATION	DEC(17,4)
	UnitItemCost	Unitary cost of Product	--
	AverageUnitItemCost	Average cost of Product	--
	ValueOfCurrentStockAmount	Current balance of stock of product in value	--

Stock Movement Transactions:  MovementsInternal_1_001.xsd 
Message Identifier: MovementsInternal
Version: 1_001
Protheus Module: SIGAPCP
Sending Type: Synchronous

Note: This message is generated by PC-Factory and sent to Protheus.

Transaction Transfers:  TransferWarehouse_1_003.xsd 
Message Identifier: TransferWarehouse 
Version: 1_003
Protheus Module: SIGAPCP
Sending Type: Synchronous

Note: This message is generated by PC-Factory and sent to Protheus.

Transaction Refusal:  Refusal_1_000.xsd
Identifier of Message: Refusal
Version: 1_000
Module Protheus: SIGAPCP
Type of Delivery: Synchronous

This message is used to register the losses of production when good spare parts are registered, then later a defect is verified. It can be used to register the losses of raw material.

Note:

This message is generated by PC-Factory and sent to Protheus.

This message will have the following purposes: 
Loss of Finished Product entering destination product:
Enables you to change certain amount that has already been registered and is in stock as good. It is called refusal of finished product, as you do not need to perform reversal and adjustment of annotation.
Example: OP of 50 units, 5 annotations of 10, Need of adjustment of 45 spare parts with deffects and 5 good.

Instead of reversing 5 annotation and register again 5 good ones and 45 scraps in ProductionAppointment, a Refusal message can be sent for OP, indicating the reason of refusal/defect and code of destination product.

Loss of Raw Material:

The message of refusal is also used to register loss of raw material during the productive process. The raw material can generated a subproduct or not.

Loss of Finished Product without entering destination product:

Used to enter the loss of finished product, without being necessary to generate the destination tags.

Note:

• Routine MATA685 is executed
• The tag IdReport is not mandatory. It indicates the production report that must be updated (Not used for Protheus)
• The tag Type, indicates whether it is Scrap. 1 = No ; 2= Yes.

General Limitations/Restrictions

The integration does not contempalte the generation of orders by APs, register through Fluig (WorkFlow) or routines not described in this document.
Build must be equal to or later than 7.00.131227A and date 9/8/2014.

Common Situations 

Possible common problematic status that can happen during the work of the integration and how to solve it.

1) When the message is sent to PCP Protheus for PC-Factory, there may be situations in which the WebService is not totally functional. In these cases, a generic error message is displayed on screen:

Unable to execute the connection with WebService of PCFactory. 

To solve this problems, check configurations of destination system, by analyzing the work of the server used for this communication and if it is enabled in WebService address. 

2) Customers with changes in dictionary with specific rules affecting the routines listed in this document.

To solve this problem, it must check dictionary and see each case.

3)Waiting time of WebService. Due to the fact that some processes take some a long time to be executed, when ERP sends return, WebService may not be waiting.

Change waiting time of WebService PC-Factory.

Application support checklist

Verification Checklist:

• In the parameters routine, PCPA109, check whether the active field is "1 - ACTIVE"
• In the parameters routine, PCPA109, tstar connection with WebService of PPI entered through the button Test.
• Configuration of sessions WEBSERVICE and PROXY from APPSERVER.INI;
• Adjust integration in relation to configuration or business.