SAP PP Pack — Production
The production pack covers what a plant needs for the shop floor to talk to SAP PP: confirm what was produced, issue what was consumed, receive the finished goods and read the order backlog to know what to do next.
Before installing, read SAP Packs — the wizard, the parameters and the reinstall rules are shared by all three packs.
The flow it solves
The classic shift cycle, with the recipe that covers each step:
Not every plant uses every step. Many start with confirmation and goods issue only, adding the rest as the MES matures.
Decisions you will have to make
Confirmation: by time ticket or by header?
| Time ticket | Header | |
|---|---|---|
| Granularity | Order operation | Whole order |
| When to use | The MES tracks the routing and knows the current operation | The MES only knows “I produced X of this order” |
| Extra field | operacao | — |
If in doubt, start with header: it asks less of the MES and is easier to get right.
There is also time event confirmation (clock in/out of the operation) and PDC upload, designed by SAP for high-volume shop-floor collectors. Both are in the catalog as non-essential recipes.
Goods issue: automatic or explicit?
If the material has backflush set in the master, the confirmation itself consumes the components and you do not need the goods issue recipe. If it does not, the MES has to send the issue separately — the common case when there is component scrap or substitution.
Production goods receipt
Movement 101 against an order requires MVT_IND = 'F' (order receipt), which the pack already
fills in. If the material is batch-managed, run the Create batch recipe first — SAP rejects the
receipt without a batch.
Gotchas in this pack
Posting period. A goods movement is an accounting posting: if the plant’s period is closed for the date you send, SAP rejects it. The pack maps this error to a readable sentence, but the fix is with finance, not with the integration.
Order not released. Confirming against an order that is not released fails. If your MES is the one deciding when to start, install the Release production order recipe too and call it before the first confirmation.
Cancelling needs the confirmation number. The cancel recipe takes numeroConfirmacao and
contadorConfirmacao, which come back in the confirmation response — store them in the MES if you
intend to allow corrections.
Summary
51 recipes — 24 collection, 27 delivery — of which 15 essential.
Recipes
Order
| Recipe | Direction | SAP function | Solves |
|---|---|---|---|
| Production order detail ·essential | Collection | BAPI_PRODORD_GET_DETAIL | The MES asks for one order and gets header, operations and components — enough to build the operator screen. |
| Plant order backlog ·essential | Collection | BAPI_PRODORD_GET_LIST | Lists the plant’s orders so the MES can build its work queue. With no input parameter it runs on the scheduler. |
| Release production order ·essential | Delivery | BAPI_PRODORD_RELEASE | Releases the order so the shop floor can confirm against it. Lets the MES trigger release without anyone opening SAP. |
| Technically complete order ·essential | Delivery | BAPI_PRODORD_COMPLETE_TECH | Marks the order technically complete when production ends — closes the cycle started by the release. |
| Order exists? | Collection | BAPI_PRODORD_EXIST_CHECK | Order exists?. Recipe generated from the BAPI_PRODORD_EXIST_CHECK signature in SAP. |
| Order component availability | Collection | BAPI_PRODORD_CHECK_MAT_AVAIL | Order component availability. Recipe generated from the BAPI_PRODORD_CHECK_MAT_AVAIL signature in SAP. |
| Process order detail (PP-PI) | Collection | BAPI_PROCORD_GET_DETAIL | Process order detail (PP-PI). Recipe generated from the BAPI_PROCORD_GET_DETAIL signature in SAP. |
| Process order list (PP-PI) | Collection | BAPI_PROCORD_GET_LIST | Process order list (PP-PI). Recipe generated from the BAPI_PROCORD_GET_LIST signature in SAP. |
| Planned order | Collection | BAPI_PLANNEDORDER_GET_DETAIL | Planned order. Recipe generated from the BAPI_PLANNEDORDER_GET_DETAIL signature in SAP. |
| Control recipe — list (PP-PI) | Collection | BAPI_CONTROL_RECIPE_GET_LIST | Control recipe — list (PP-PI). Recipe generated from the BAPI_CONTROL_RECIPE_GET_LIST signature in SAP. |
| Control recipe — download (PP-PI) | Collection | BAPI_CONTROL_RECIPE_REQUEST | Control recipe — download (PP-PI). Recipe generated from the BAPI_CONTROL_RECIPE_REQUEST signature in SAP. |
| Create order | Delivery | BAPI_PRODORD_CREATE | Create order. Recipe generated from the BAPI_PRODORD_CREATE signature in SAP. |
| Convert planned order into order | Delivery | BAPI_PRODORD_CREATE_FROM_PLORD | Convert planned order into order. Recipe generated from the BAPI_PRODORD_CREATE_FROM_PLORD signature in SAP. |
| Change order | Delivery | BAPI_PRODORD_CHANGE | Change order. Recipe generated from the BAPI_PRODORD_CHANGE signature in SAP. |
| Reschedule order | Delivery | BAPI_PRODORD_SCHEDULE | Reschedule order. Recipe generated from the BAPI_PRODORD_SCHEDULE signature in SAP. |
| Close order | Delivery | BAPI_PRODORD_CLOSE | Close order. Recipe generated from the BAPI_PRODORD_CLOSE signature in SAP. |
| Create planned order | Delivery | BAPI_PLANNEDORDER_CREATE | Create planned order. Recipe generated from the BAPI_PLANNEDORDER_CREATE signature in SAP. |
| Change planned order | Delivery | BAPI_PLANNEDORDER_CHANGE | Change planned order. Recipe generated from the BAPI_PLANNEDORDER_CHANGE signature in SAP. |
| Process messages (PP-PI) | Delivery | BAPI_PROCESS_MESSAGE_CREATEMLT | Process messages (PP-PI). Recipe generated from the BAPI_PROCESS_MESSAGE_CREATEMLT signature in SAP. |
| Process message already exists? | Delivery | BAPI_PROCESS_MESSAGE_CHK_EXIST | Process message already exists?. Recipe generated from the BAPI_PROCESS_MESSAGE_CHK_EXIST signature in SAP. |
Production confirmation
| Recipe | Direction | SAP function | Solves |
|---|---|---|---|
| Confirmation proposal ·essential | Collection | BAPI_PRODORDCONF_GET_TT_PROP | Before confirming, the MES asks SAP for the proposed quantities and times and shows a pre-filled screen — fewer operator typos. |
| Time ticket confirmation ·essential | Delivery | BAPI_PRODORDCONF_CREATE_TT | The MES sends yield, scrap, rework and times for one order operation. The most common shop-floor confirmation. |
| Order header confirmation ·essential | Delivery | BAPI_PRODORDCONF_CREATE_HDR | Confirms the whole order at once, with no operation detail. For MES setups that do not track routings. |
| Cancel confirmation ·essential | Delivery | BAPI_PRODORDCONF_CANCEL | Cancels a confirmation posted by mistake. Without it, fixing a confirmation means manual work in SAP. |
| Header confirmation proposal | Collection | BAPI_PRODORDCONF_GET_HDR_PROP | Header confirmation proposal. Recipe generated from the BAPI_PRODORDCONF_GET_HDR_PROP signature in SAP. |
| Confirmation proposal (PP-PI) | Collection | BAPI_PROCORDCONF_GET_TT_PROP | Confirmation proposal (PP-PI). Recipe generated from the BAPI_PROCORDCONF_GET_TT_PROP signature in SAP. |
| Confirmations already posted | Collection | BAPI_PRODORDCONF_GETLIST | Confirmations already posted. Recipe generated from the BAPI_PRODORDCONF_GETLIST signature in SAP. |
| Confirmation detail | Collection | BAPI_PRODORDCONF_GETDETAIL | Confirmation detail. Recipe generated from the BAPI_PRODORDCONF_GETDETAIL signature in SAP. |
| Time event confirmation (clock in/out of the operation) | Delivery | BAPI_PRODORDCONF_CREATE_TE | Time event confirmation (clock in/out of the operation). Recipe generated from the BAPI_PRODORDCONF_CREATE_TE signature in SAP. |
| Activity confirmation | Delivery | BAPI_PRODORDCONF_CREATE_ACT | Activity confirmation. Recipe generated from the BAPI_PRODORDCONF_CREATE_ACT signature in SAP. |
| PDC upload of time ticket confirmations | Delivery | BAPI_PRODORDCONF_PDC_UPLOAD_TT | PDC upload of time ticket confirmations. Recipe generated from the BAPI_PRODORDCONF_PDC_UPLOAD_TT signature in SAP. |
| PDC upload of time events | Delivery | BAPI_PRODORDCONF_PDC_UPLOAD_TE | PDC upload of time events. Recipe generated from the BAPI_PRODORDCONF_PDC_UPLOAD_TE signature in SAP. |
| PP-PI time ticket confirmation | Delivery | BAPI_PROCORDCONF_CREATE_TT | PP-PI time ticket confirmation. Recipe generated from the BAPI_PROCORDCONF_CREATE_TT signature in SAP. |
| PP-PI header confirmation | Delivery | BAPI_PROCORDCONF_CREATE_HDR | PP-PI header confirmation. Recipe generated from the BAPI_PROCORDCONF_CREATE_HDR signature in SAP. |
| Cancel confirmation (PP-PI) | Delivery | BAPI_PROCORDCONF_CANCEL | Cancel confirmation (PP-PI). Recipe generated from the BAPI_PROCORDCONF_CANCEL signature in SAP. |
Master data
| Recipe | Direction | SAP function | Solves |
|---|---|---|---|
| Material master ·essential | Collection | BAPI_MATERIAL_GET_DETAIL | Brings description, unit and plant data for a material — the master data the MES needs to mirror. |
| Bill of material ·essential | Collection | CSAP_MAT_BOM_READ | Expected components of a material — used by the MES to check what was actually consumed against what was planned. |
| Batch detail ·essential | Collection | BAPI_BATCH_GET_DETAIL | Data for one batch — the traceability base when the MES needs shelf life, vendor or status. |
| Create batch ·essential | Delivery | BAPI_BATCH_CREATE | Creates the batch in SAP ahead of the goods receipt, when the MES owns the plant’s batch numbering. |
| Material list | Collection | BAPI_MATERIAL_GETLIST | Material list. Recipe generated from the BAPI_MATERIAL_GETLIST signature in SAP. |
| Availability (ATP) | Collection | BAPI_MATERIAL_AVAILABILITY | Availability (ATP). Recipe generated from the BAPI_MATERIAL_AVAILABILITY signature in SAP. |
| Stock and requirements | Collection | BAPI_MATERIAL_STOCK_REQ_LIST | Stock and requirements. Recipe generated from the BAPI_MATERIAL_STOCK_REQ_LIST signature in SAP. |
| Bill of material exists? | Collection | BAPI_MAT_BOM_EXISTENCE_CHECK | Bill of material exists?. Recipe generated from the BAPI_MAT_BOM_EXISTENCE_CHECK signature in SAP. |
| Routing exists? | Collection | BAPI_ROUTING_EXISTENCE_CHECK | Routing exists?. Recipe generated from the BAPI_ROUTING_EXISTENCE_CHECK signature in SAP. |
| Batch characteristics (classification) | Collection | BAPI_OBJCL_GETDETAIL | Batch characteristics (classification). Recipe generated from the BAPI_OBJCL_GETDETAIL signature in SAP. |
| Change batch | Delivery | BAPI_BATCH_CHANGE | Change batch. Recipe generated from the BAPI_BATCH_CHANGE signature in SAP. |
| Batch characteristics | Delivery | BAPI_OBJCL_CHANGE | Batch characteristics. Recipe generated from the BAPI_OBJCL_CHANGE signature in SAP. |
Goods movement
| Recipe | Direction | SAP function | Solves |
|---|---|---|---|
| Component goods issue ·essential | Delivery | BAPI_GOODSMVT_CREATE | Issues a component against the production order (movement {{MOV_CONSUMO}}). The physical counterpart of the confirmation. |
| Production goods receipt ·essential | Delivery | BAPI_GOODSMVT_CREATE | Posts the order’s finished goods into stock (movement {{MOV_ENTRADA}}), with batch when applicable. |
| Cancel material document ·essential | Delivery | BAPI_GOODSMVT_CANCEL | Cancels a material document posted by mistake, given its number and year. |
| Movements already posted | Collection | BAPI_GOODSMVT_GETITEMS | Movements already posted. Recipe generated from the BAPI_GOODSMVT_GETITEMS signature in SAP. |
Field contracts
Production order detail
PREFIXO_PP_ORDEM_DETALHE — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
ordem | yes | NUMBER |
Plant order backlog
PREFIXO_PP_ORDEM_LISTA — Your system provides these fields when calling the collection URL.
Needs review before activating. Created inactive on purpose: it sweeps the whole plant backlog on every run. Set the interface schedule and activate once you decide the frequency.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Confirmation proposal
PREFIXO_PP_APONT_PROPOSTA — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
ordem | yes | TIMETICKETS.ORDERID |
operacao | yes | TIMETICKETS.OPERATION |
Material master
PREFIXO_PP_MATERIAL — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
material | yes | MATERIAL |
Bill of material
PREFIXO_PP_BOM — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
material | yes | MATERIAL |
Batch detail
PREFIXO_PP_LOTE — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
material | yes | MATERIAL |
lote | yes | BATCH |
Time ticket confirmation
PREFIXO_PP_APONT_TEMPO — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
ordem | yes | TIMETICKETS.ORDERID |
operacao | yes | TIMETICKETS.OPERATION |
quantidadeBoa | yes | TIMETICKETS.YIELD |
quantidadeRefugo | — | TIMETICKETS.SCRAP |
quantidadeRetrabalho | — | TIMETICKETS.REWORK |
unidade | yes | TIMETICKETS.CONF_QUAN_UNIT |
apontamentoFinal | — | TIMETICKETS.FIN_CONF |
dataLancamento | — | TIMETICKETS.POSTG_DATE |
motivoDesvio | — | TIMETICKETS.DEV_REASON |
observacao | — | TIMETICKETS.CONF_TEXT |
Order header confirmation
PREFIXO_PP_APONT_ORDEM — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
ordem | yes | ATHDRLEVELS.ORDERID |
quantidadeBoa | yes | ATHDRLEVELS.YIELD |
quantidadeRefugo | — | ATHDRLEVELS.SCRAP |
unidade | yes | ATHDRLEVELS.CONF_QUAN_UNIT |
apontamentoFinal | — | ATHDRLEVELS.FIN_CONF |
dataLancamento | — | ATHDRLEVELS.POSTG_DATE |
Cancel confirmation
PREFIXO_PP_APONT_ESTORNO — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
numeroConfirmacao | yes | CONFIRMATION |
contadorConfirmacao | yes | CONFIRMATIONCOUNTER |
dataLancamento | — | POSTG_DATE |
observacao | — | CONF_TEXT |
Component goods issue
PREFIXO_PP_CONSUMO — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
ordem | yes | GOODSMVT_ITEM.ORDERID |
material | yes | GOODSMVT_ITEM.MATERIAL |
quantidade | yes | GOODSMVT_ITEM.ENTRY_QNT |
unidade | yes | GOODSMVT_ITEM.ENTRY_UOM |
deposito | — | GOODSMVT_ITEM.STGE_LOC |
lote | — | GOODSMVT_ITEM.BATCH |
motivoMovimento | — | GOODSMVT_ITEM.MOVE_REAS |
dataLancamento | yes | GOODSMVT_HEADER.PSTNG_DATE |
documentoReferencia | — | GOODSMVT_HEADER.REF_DOC_NO |
observacao | — | GOODSMVT_HEADER.HEADER_TXT |
Production goods receipt
PREFIXO_PP_ENTRADA — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
ordem | yes | GOODSMVT_ITEM.ORDERID |
material | yes | GOODSMVT_ITEM.MATERIAL |
quantidade | yes | GOODSMVT_ITEM.ENTRY_QNT |
unidade | yes | GOODSMVT_ITEM.ENTRY_UOM |
deposito | — | GOODSMVT_ITEM.STGE_LOC |
lote | — | GOODSMVT_ITEM.BATCH |
dataLancamento | yes | GOODSMVT_HEADER.PSTNG_DATE |
observacao | — | GOODSMVT_HEADER.HEADER_TXT |
Cancel material document
PREFIXO_PP_MOV_ESTORNO — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
documentoMaterial | yes | MATERIALDOCUMENT |
anoDocumento | yes | MATDOCUMENTYEAR |
dataLancamento | — | GOODSMVT_PSTNG_DATE |
Release production order
PREFIXO_PP_LIBERAR — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
ordem | yes | ORDERS.ORDER_NUMBER |
Technically complete order
PREFIXO_PP_ENCERRAR_TEC — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
ordem | yes | ORDERS.ORDER_NUMBER |
Create batch
PREFIXO_PP_LOTE_CRIAR — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
material | yes | MATERIAL |
lote | yes | BATCH |
dataProducao | — | BATCHATTRIBUTES.PROD_DATE |
dataValidade | — | BATCHATTRIBUTES.EXPIRYDATE |
loteFornecedor | — | BATCHATTRIBUTES.VENDRBATCH |
Order exists?
PREFIXO_PP_PRODORD_EXIST_CHECK — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
numero | yes | NUMBER |
Order component availability
PREFIXO_PP_PRODORD_CHECK_MAT_AVAIL — Your system provides these fields when calling the collection URL.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Process order detail (PP-PI)
PREFIXO_PP_PROCORD_GET_DETAIL — Your system provides these fields when calling the collection URL.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a estrutura ORDER_OBJECTS. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
| Field | Required | SAP field |
|---|---|---|
numero | yes | NUMBER |
Process order list (PP-PI)
PREFIXO_PP_PROCORD_GET_LIST — Your system provides these fields when calling the collection URL.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Header confirmation proposal
PREFIXO_PP_PRODORDCONF_GET_HDR_PROP — Your system provides these fields when calling the collection URL.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Confirmation proposal (PP-PI)
PREFIXO_PP_PROCORDCONF_GET_TT_PROP — Your system provides these fields when calling the collection URL.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Confirmations already posted
PREFIXO_PP_PRODORDCONF_GETLIST — Your system provides these fields when calling the collection URL.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Confirmation detail
PREFIXO_PP_PRODORDCONF_GETDETAIL — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
numeroConfirmacao | yes | CONFIRMATION |
contadorConfirmacao | yes | CONFIRMATIONCOUNTER |
Planned order
PREFIXO_PP_PLANNEDORDER_GET_DETAIL — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
plannedorder | yes | PLANNEDORDER |
Material list
PREFIXO_PP_MATERIAL_GETLIST — Your system provides these fields when calling the collection URL.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Availability (ATP)
PREFIXO_PP_MATERIAL_AVAILABILITY — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
material | yes | MATERIAL |
centro | yes | PLANT |
unidade | yes | UNIT |
Stock and requirements
PREFIXO_PP_MATERIAL_STOCK_REQ_LIST — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
material | yes | MATERIAL |
Bill of material exists?
PREFIXO_PP_MAT_BOM_EXISTENCE_CHECK — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
bomusage | yes | BOMUSAGE |
material | yes | MATERIAL |
Routing exists?
PREFIXO_PP_ROUTING_EXISTENCE_CHECK — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
group | yes | GROUP |
groupcounter | yes | GROUPCOUNTER |
Batch characteristics (classification)
PREFIXO_PP_OBJCL_GETDETAIL — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
classnum | yes | CLASSNUM |
classtype | yes | CLASSTYPE |
objectkey | yes | OBJECTKEY |
objecttable | yes | OBJECTTABLE |
Movements already posted
PREFIXO_PP_GOODSMVT_GETITEMS — Your system provides these fields when calling the collection URL.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Control recipe — list (PP-PI)
PREFIXO_PP_CONTROL_RECIPE_GET_LIST — Your system provides these fields when calling the collection URL.
| Field | Required | SAP field |
|---|---|---|
centro | yes | PLANT |
Control recipe — download (PP-PI)
PREFIXO_PP_CONTROL_RECIPE_REQUEST — Your system provides these fields when calling the collection URL.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Time event confirmation (clock in/out of the operation)
PREFIXO_PP_PRODORDCONF_CREATE_TE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela TIMEEVENTS. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Activity confirmation
PREFIXO_PP_PRODORDCONF_CREATE_ACT — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela ACTIVITIES. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
PDC upload of time ticket confirmations
PREFIXO_PP_PRODORDCONF_PDC_UPLOAD_TT — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela TIMETICKETS. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
PDC upload of time events
PREFIXO_PP_PRODORDCONF_PDC_UPLOAD_TE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela TIMEEVENTS. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
PP-PI time ticket confirmation
PREFIXO_PP_PROCORDCONF_CREATE_TT — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela TIMETICKETS. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
PP-PI header confirmation
PREFIXO_PP_PROCORDCONF_CREATE_HDR — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela ATHDRLEVELS. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Cancel confirmation (PP-PI)
PREFIXO_PP_PROCORDCONF_CANCEL — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
numeroConfirmacao | yes | CONFIRMATION |
contadorConfirmacao | yes | CONFIRMATIONCOUNTER |
Create order
PREFIXO_PP_PRODORD_CREATE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a estrutura ORDERDATA. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Convert planned order into order
PREFIXO_PP_PRODORD_CREATE_FROM_PLORD — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
plannedOrder | yes | PLANNED_ORDER |
Change order
PREFIXO_PP_PRODORD_CHANGE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a estrutura ORDERDATA; preencher a estrutura ORDERDATAX. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
| Field | Required | SAP field |
|---|---|---|
numero | yes | NUMBER |
Reschedule order
PREFIXO_PP_PRODORD_SCHEDULE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela ORDERS. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Close order
PREFIXO_PP_PRODORD_CLOSE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela ORDERS. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Change batch
PREFIXO_PP_BATCH_CHANGE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a estrutura BATCHATTRIBUTES; preencher a estrutura BATCHATTRIBUTESX. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
| Field | Required | SAP field |
|---|---|---|
lote | yes | BATCH |
material | yes | MATERIAL |
Batch characteristics
PREFIXO_PP_OBJCL_CHANGE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela ALLOCVALUESCHARNEW; preencher a tabela ALLOCVALUESCURRNEW; preencher a tabela ALLOCVALUESNUMNEW. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
| Field | Required | SAP field |
|---|---|---|
classnum | yes | CLASSNUM |
classtype | yes | CLASSTYPE |
objectkey | yes | OBJECTKEY |
objecttable | yes | OBJECTTABLE |
Create planned order
PREFIXO_PP_PLANNEDORDER_CREATE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a estrutura HEADERDATA. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Change planned order
PREFIXO_PP_PLANNEDORDER_CHANGE — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a estrutura HEADERDATA; preencher a estrutura HEADERDATAX. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
| Field | Required | SAP field |
|---|---|---|
plannedorder | yes | PLANNEDORDER |
Process messages (PP-PI)
PREFIXO_PP_PROCESS_MESSAGE_CREATEMLT — Your system sends these fields in the message body.
Needs review before activating. Created INACTIVE: the pack cannot guess the content — preencher a tabela PROCMESSCHARAC; preencher a tabela PROCMESSHEADER. Open the definition, use the “SAP Function Parameters” popup to fill it in, then activate.
No input fields: the recipe runs on the scheduler, with the values fixed in the pack parameters.
Process message already exists?
PREFIXO_PP_PROCESS_MESSAGE_CHK_EXIST — Your system sends these fields in the message body.
| Field | Required | SAP field |
|---|---|---|
processmessage | yes | PROCESSMESSAGE |