Histórico da Página

...

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.

Abaixo tabela dos códigos enviadosCheck below, table of sent codes:

ImportanteImportant:

• 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
• Caso um registro fique preso com status de "registro em processamento", este poderá ser destravado pela rotina PCPA112, incluindo o IDMES correspondente.
• O reprocessamento de uma mensagem com ERRO(2) pode ser feito passando a tag Reprocess = true.
  Exemplo Example:

<BusinessEvent>

            <Entity>productionappointment</Entity>

...

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

...

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

...

• 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

...