Histórico da Página

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 PCP 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

...

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:

...

• 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.

...

• 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.

...

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.

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.

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 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:: MTI650UMOPMTI650FCOP_Change_conversion_factor_second_unit_of_operation_measure_of_operation_adapter_productionnproduction_order.

RegistersProduction Order: 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.

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

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

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
  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.

• 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.

Image Removed

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.

Image Removed

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

Image Removed

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

Image Removed

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

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.

Image Added

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.

Image Added

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

Image Added

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

Image Added

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

SFC Resource Transaction: Resource_1_000
Message Identifier: Resource
Version: 1_000
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

...

...

...

• The Resource in the PCP indicates the machine, in the shop floor indicates toosl, operator etc;
• When origin is PCP the tag Type (Resource Type) is generated in fixed value '2';
• When origin is PCP the tag UnitCycleQuantity (Cycles Unit) is generated in fixed value '1';
• When origin is PCP the tag UnitCycleQuantity (Cycles Unit) is generated in fixed value '1';
• When origin is PCP the tag StartExpirationDate (Start Validity) is generated with date of message generation;
• When origin is PCP the tag EndExpirationDate (End Validity) is generated in fixed value '1';
  Current date (dDataBase) + lifespan of tool (H4_VIDAUTI). Consider type of lifec ycle (H4_TIPOVID) - D=Days;H=Hours;M=Month;A=Year

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

Script Transaction - Item Operations: ItemScript_1_000.xsd 
Message Identifier: ItemScript
Version: 1_000
Protheus Module: SiGAPCP
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: ItemStructureAddresses Transaction: AdressStock_1_000.xsd 
Message IdenfierIdentifier: AdressStockItemStructure
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

CHAR(15DESCCHAR30ListOfStockReferenceCode 02 CHAR(10)CHAR(15DATEDEC(12BookedStockAmountDEC(12,2) QuantityUpdatedUpdated QuantityDEC(12,2)1=Input or 2=Output.01

TBLInWOHD.ProductCode TBLInWOHD.WOCode	CHAR(30
Message	Tag	Description	Table/Field: Protheus	Type	Table/Field: PC-Factory	Type
BusinessContentType	ItemCode	Product code	SB2.B2_COD	)
		ItemAmount	Base quantity of parent item		ItemDescription	Item Description	SB1.B1_	QB	NUM(	07)			TBLInWOHD.TotalQTY	DEC(19,4)
ItemComponentType
	ItemSequence	Reference	--			Sequence of component	SG1.G1_TRT	NUM(05)	TBLInBillMat.BillMatExtCode	CHAR(20)
	WarehouseCode	Deposit/Stock location/Warehouse	ItemComponentCode	Code item component	SG1.G1_COMPSB2.B2_LOCAL	CHAR(	15)		TBLInBillMat.ProductCode	CHAR(20)
	LotCode	Lot Number	SB8.B8_LOTECTL	ItemComponentInternalId	Internal Id of Item Component	COMPANY + SG1.G1_BRANCH + SG1.G1_COMP
	SubLotCode	Sub-lot	SB8.B8_NUMLOTE	CHAR(06)
	NumberSeries	Serial Number	SBF.BF_NUMSERI	CHAR(20)
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		AddressCode	Address/Location	SBF.BF_LOCALIZ	)
	LotDueDate	Expiration Date	SB8.B8_DTVALID	ItemComponentAmount	Quantity of component item	SG1.G1_QUANT	DEC(12,6)
	CurrentStockAmount	Stock balance	SB2.B2_QATU SB8.B8_SALDO SBF.BF_QUANT	LossFactor	Factor of loss	SG1.G1_LOSS	DEC(05,2)
ListOfScript			Reserved Quantity	SB2.B2_RESERVA SB8.B8_EMPENHO SBF.BF_EMPENHO
	Scriptcode	Code of Script	SGF.GF_SCRIPT	CHAR(02)	TBLInWOHD.ExtCode	CHAR(20)
	ScriptAlternative	Alternative of Script	--	AvailableStockAmount	Available balance	SB2.B2_QATU - SB2.B2_RESERVA SB8.B8_SALDO - SB8.B8_EMPENHO SBF.BF_QUANT - SBF.BF_EMPENHO	DEC(12,2)
		ActivityIntenalID	ID Operation	--
	InputOutput	Input or Output	ActivityCode	Code of Operation	SGF.GF_OPERAC	CHAR(02)	TBLInWodet.Code	CHAR(	10)
	ActivityComponentSequence

Waste Reason Transaction: WasteReason_1_000.xsd 

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

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

Stop Reason Transaction: StopReason_1_000.xsd

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