Definition of the Interface The following section gives you an overview and a detailed description of the event parameters for the object type /SAPAPO/MF and for the event TPOINT_REACHED.
You can display the definition of the parameters by calling up the
Business Object Builder
(transaction SWO1). There, you also find documentation on how to connect the Action Handler to the external production system.
|
|
|
|---|---|---|
Parameter |
Object Type |
DDIC Structure |
TableOfEvents |
/SAPAPO/MF |
/SAPAPO/AHT_EVENTPARA_STR |
TableOfEvents2 |
/SAPAPO/MF |
/SAPAPO/AHT_EVENT2PARA_STR |
TableOfMapping |
/SAPAPO/MF |
/SAPAPO/AHT_MAPPARA_STR |
TableOfConfirms |
/SAPAPO/MF |
/SAPAPO/AHT_PPC_INPUT |
TableOfOrders |
/SAPAPO/MF |
/SAPAPO/AHT_ORDERPARA_STR |
TableOfOrders2 |
/SAPAPO/MF |
/SAPAPO/AHT_ORDER2PARA_STR |
TableOfCustomerData |
/SAPAPO/MF |
/SAPAPO/AHT_CUSTOMERPARA_STR |
StrategieProfil |
/SAPAPO/MF |
/SAPAPO/CDPS_STRPRO_ID |
PlanningVersion |
/SAPAPO/MF |
/SAPAPO/AHT_SIMID_EXT |
CheckUpdateProfile |
/SAPAPO/MF |
/SAPAPO/AHT_PROF_CHKUPD |
This parameter is the anchor table of the Action Handler and has the unique key EVTID . The field EVTID must always be filled, since it establishes the connection to the other parameters. The context controls which other fields need to be filled:
Triggers from the production line: call with TPOINT and ORDNO (or EXTID). Example: The order 4711 has reached the
Start
of
Final
Assembly
point.
Carry out actions of an action network: call with ORDNO (or EXTID), ACTION and REF2NET. Example: An action network, which consists of the action sequence
Check
solvency
of
customer
and
Check
component
a
v
ailability, has been assigned to the order in order to represent the preparation of the production process.
Carry out standalone actions: call with ORDNO (or EXTID) and ACTION. Example: You want to carry out actions which can be carried out without any context, such as, for example,
Assign
action
network
.
Note
Field SUBCNT: Some events trigger the processing of optional action points that can be carried out retroactively. Events are created internally for these action points. The new events inherit the EVTID of the original event and also receive a counter which enables you to distinguish them from original events. Therefore, you can recognize that an event has been generated because its counter does not have the initial value.
The field is only used internally; it must not be filled externally!
TableOfEvents |
Header Data of the Event |
|
|---|---|---|
Component |
Component Type |
Remark |
EVTID |
/SAPAPO/AHT_EVENTID |
ID for pointing with additional tables |
SUBCNT |
/SAPAPO/AHT_EVENT_SUBCOUNT |
Additional number (ID) for generated events |
TPOINT |
/SAPAPO/AHT_TRACK_TP |
Action point |
ORDNO |
/SAPAPO/AHT_ORDNO |
Order number |
EXTID |
/SAPAPO/AHT_EXTID |
Alternative order ID (optional) |
ACTION |
/SAPAPO/AHT_ACTION |
Action (optional) |
REF2NET |
/SAPAPO/AHT_REF2NET |
Indicator: action with reference to an action network |
EXTTS |
/SAPAPO/AHT_TIMESTAMPC |
External time stamp |
EXTTZ |
/SAPAPO/AHT_EXTTZ |
Time zone |
QUANT |
/SAPAPO/AHT_QUANT_IF |
Quantity |
MEINS |
/SAPAPO/AHT_MEINS |
Base unit of measure |
.INCLUDE |
CI_AHT_EVENTPARA_STR |
Customer-specific additional fields |
This parameter ensures the data security. The parameter is optional; if you do not set it, the system can subsequently process a set of events twice. Example: The system crashes while a part of the event is being processed and posted. The event is in the event queue of the workflow (transaction SWEQADM) or in the RFC monitor (transaction SM58). If you trigger the event again, it is processed completely. For more information, see the Data Security Concept .
If you use this parameter, you need to make sure that you regularly delete old entries from the /SAPAPO/AHT_EVAC database table. To do so, you can use the report /SAPAPO/AHT_CLEAR_EVAC, for example. Reason: The database table shows which events have already been partially processed.
TableOfEvents |
Further Header Data for the Event |
|
|---|---|---|
Component |
Component Type |
Remark |
EVTID |
/SAPAPO/AHT_EVENTID |
ID for pointing with additional tables |
EVENT_GUID |
BAPIGUID_32 |
External name for the set of events |
You use this parameter in flexible order transactions (FOT) in order to define how quantities which have been partially confirmed (work in process) are transferred from one reporting point structure to another.
TableOfMapping |
Data for Transfer of WIP |
|
|---|---|---|
Component |
Component Type |
Remark |
EVTID |
/SAPAPO/AHT_EVENTID |
ID for pointing with additional tables |
ORDNO |
/SAPAPO/AHT_ORDNO |
Order number |
EXTID |
/SAPAPO/AHT_EXTID |
Alternative order ID (optional) |
RPTFR |
/SAPAPO/PPC_RPTNAM |
Initial reporting point |
RPTTO |
/SAPAPO/PPC_RPTNAM |
Target reporting point |
WIP_QTY |
/SAPAPO/AHT_QUANT_IF |
WIP quantity to be transferred |
MEINS |
/SAPAPO/AHT_MEINS |
Base unit of measure |
This parameter contains confirmation records that are evaluated by the action 01SAP_PRODUCTION_TRACKING. Confirmations can be made in three different ways:
using the planned order number; in this case the parameter TableOfEvents contains the order number
using the sales order number: in this case the fields KDAUF, KDPOS and LOGSYS have to be fed with data
using the material number and the location; in this case you have to enter MATNR and LOCNO
TableOfConfirms |
Data for the Confirmation |
|
|---|---|---|
Component |
Component Type |
Remark |
EVTID |
/SAPAPO/AHT_EVENTID |
ID for pointing with header segment |
KDAUF |
/SAPAPO/PPC_... |
Sales order |
KDPOS |
/SAPAPO/PPC_... |
Sales order item |
LOGSYS |
/SAPAPO/PPC_... |
Logical system of sales order |
MATNR |
/SAPAPO/PPC_... |
Material |
LOCNO |
/SAPAPO/PPC_... |
Location |
CQUAN |
/SAPAPO/PPC_... |
Confirmation quantity |
CUNIT |
/SAPAPO/PPC_… |
Unit of measurement of confirmation quantity |
This parameter contains the objects (orders) to be manipulated, including all parameters that are needed for the actions 01SAP_PRODUCTION_TRACKING (production tracking), 01SAP_ORDER_MODIFY_GENERIC (order change) and 01SAP_ALTERNATIVE_LINE_SWITCH (iPPE line change). The order in this segment can have a separate time stamp.
TableOfOrders |
Data for the Order |
|
|---|---|---|
Component |
Component Type |
Remark |
EVTID |
/SAPAPO/AHT_EVENTID |
ID for pointing with header segment |
PLINE |
/SAPAPO/AHT_LINE |
Production line (optional if iPPE is used) |
RESNA |
/SAPAPO/AHT_RESNAME |
Resource (optional if iPPE is used) |
ACTST |
/SAPAPO/AHT_ACTIVITY_STATUS |
New status (optional in case of rescheduling) |
ACTYP |
/SAPAPO/AHT_ACTTYPE |
Activity type (optional; default:
|
ASTTS |
/SAPAPO/AHT_TIMESTAMPC |
New starting point (obligatory in case of forward scheduling). The PP/DS strategy is determined via the parameter
|
AENTS |
/SAPAPO/AHT_TIMESTAMPC |
New end time (obligatory in case of backward scheduling). The PP/DS strategy is determined via the parameter
|
NOCHK |
/SAPAPO/AHT_NOCHECK4ACTST |
No check for ascending order of activity status |
.INCLUDE |
CI_AHT_ORDERPARA_STR |
Customer-specific additional fields |
You use this parameter in flexible order transactions (FOT) in order to create orders, either with reference to a sales order or with reference to a product variant.
TableOfOrders2 |
Further Data for the Order |
|
|---|---|---|
Component |
Component Type |
Remark |
EVTID |
/SAPAPO/AHT_EVENTID |
ID for pointing with header segment |
ORDNO |
/SAPAPO/AHT_ORDNO |
Order number |
EXTID |
/SAPAPO/AHT_EXTID |
Alternative order ID (optional) |
LOCNO |
/SAPAPO/LOCNO |
Location |
MATNR |
/SAPAPO/MATNR |
Product |
PPENA |
PPE_NAME |
Production version |
SO_DELNR |
/SAPAPO/DELNR |
Schedule line |
SO_POSNR |
/SAPAPO/POSNR |
Item |
SO_LOGSYS |
LOGSYS |
Logical system |
QTY_TOTAL |
/SAPAPO/AHT_QUANT_IF |
Desired quantity |
QTY_RECEIPT |
/SAPAPO/AHT_QUANT_IF |
Confirmed quantity |
QTY_SCRAP |
/SAPAPO/AHT_QUANT_IF |
Scrap |
MEINS |
/SAPAPO/ |
Base unit of measure |
CALC_SCRAP |
/SAPAPO/BOOLEAN |
Calculate scrap |
This parameter provides the opportunity to pass on customer-specific parameters in order to supply customer-specific actions with data.
TableOfCustomerData |
Data of Customer |
|
|---|---|---|
Component |
Component Type |
Remark |
EVTID |
/SAPAPO/AHT_EVENTID |
ID for pointing with header segment |
.INCLUDE |
CI_AHT_CUSTOMERPARA_STR |
Customer-specific additional fields |
The PP/DS strategy profile is an optional parameter which can control the strategy when order activities are rescheduled during the action 01SAP_ORDER_MODIFY_GENERIC (order change). The action 01SAP_ALTERNATIVE_LINE_SWITCH (iPPE line switch) also uses the strategy, since scheduling is carried out every time a line is switched.
You define the profile in PP/DS Customizing. Depending on the strategy, the system uses different components of the parameter
TableOfOrders
. When you use backward scheduling, the component AENTS (end date) is used, when you use forward scheduling, the component ASTTS (start date) is used. If the planning profile consists of several prioritized individual strategies, both components are used.
If no profile has been specified explicitly, the system uses infinite planning with backward scheduling as a default.
The planning version is an optional parameter; as a default, the system uses the active planning version 000.
This optional parameter determines how the events contained in the TableOfEvents parameter are to be checked. The profile groups check and update function modules for three different scenarios of the Action Handler (notification of an order at an action point, execution of an action for an order with or without reference to an action network).
There are four different kinds of function modules:
check of ‘order-to-action point’ events
update of the action point status of the order according to the last ‘order-to-action point event’ to be carried out successfully
check of events that carry out an action for an order (with or without reference to an action network)
update of the action status of the order according to the last action to be carried out successfully
If you do not specify which profile is to be used, the system uses the profile which is marked as active in Customizing.
You can attach several confirmation documents for the same order to each event entry. The connection is established via a unique EVTID (there are no naming conventions for the event ID)
You only use the action point for the TableOfEvents parameter to determine the action 01SAP_PRODUCTION_TRACKING, the reporting point (=action point) and the order number.
Parameter(30) |
Value(255) |
Remark |
|---|---|---|
TableOfEvents |
0001 TRACKING_POINT_01 000000004711 ZZ... |
Header record of the first event |
TableOfOrders |
0001 <EXTTS>... |
Tracking&OrderModify record |
TableOfConfirms |
0001 <KDAUF><KDPOS>... |
Confirmation record |
TableOfEvents |
0002 TRACKING_POINT_02 000000000815 ZZ... |
Header record of the second event |
TableOfConfirms |
0002 <KDAUF><KDPOS>... |
Confirmation record |
TableOfEvents |
0003 TRACKING_POINT_12 000000006666 ZZ... |
Header record of the third event |
TableOfOrders |
0003 <EXTTS>... |
Tracking&OrderModify record |