Functional Specification

WuXi STA Pharmaceuticals

Project EBR SAP – PAS-X – LIMS

Integration

FS. M. 4
Document control

Approval signatures
Prepared by
Name, title, company Signature Date

Reviewed by
Name, title, company Signature Date

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 2 of 61
 Approved by
Name, title, company Signature Date

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 3 of 61
Revision History
Version Date Revised by Comments
0.1 24.05.22 Initial draft

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 4 of 61
 Contents
1 Enterprise Resources Planning Interface...................................................................
1.1 General Design & Business Processes.....................................................8
1.1.1 Master data........................................................................................13
[Link] Material Master Data.................................................................13
[Link] Master Recipe (BOM & Routing)..............................................14
1.1.2 Quality Assurance.............................................................................16
[Link] Batch Master..............................................................................16
[Link] Sample Id Announcement........................................................18
[Link] IPC Result..................................................................................18
1.1.3 Scheduling......................................................................................... 19
[Link] Process Orders.........................................................................19
1.1.4 Preparation........................................................................................20
1.1.5 Execution........................................................................................... 22
[Link] Start of Manufacturing Order...................................................22
[Link] Performance Data of Shop Floor Order...................................23
[Link] Take out on Manufacturing Order............................................23
[Link] Stock Creation on Manufacturing Order.................................23
[Link] End of Manufacturing Order.....................................................23
[Link] Abortion of Manufacturing Order.............................................23
[Link] EBR Approval Status................................................................24
1.1.6 Warehouse Management..................................................................25
[Link] Incoming Transport...................................................................31
[Link] Outgoing Transport...................................................................32
[Link] Permanent Inventory.................................................................33
[Link] Inventory Reconciliation...........................................................33
2 Technical Design.........................................................................................................
2.1 Interface Layers.........................................................................................35
2.2 Interface Technology................................................................................35
2.2.1 WXI interface.....................................................................................36
2.3 Restart Behavior........................................................................................ 36
2.4 Error Handling...........................................................................................36
2.4.1 System Behavior...............................................................................36
2.4.2 User Behavior....................................................................................36
2.5 General Conditions...................................................................................37
3 Data Formats...............................................................................................................
4 Message Structure......................................................................................................
5 Message Content.........................................................................................................
5.1 Overview.................................................................................................... 44
5.2 Master Data................................................................................................ 44
5.2.1 Message Material Master Data.........................................................44
5.2.2 Message Master Recipe (BOM & Routing)......................................48

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 5 of 61
 5.3 Quality Control.......................................................................................... 51
5.3.1 Message Batch Data.........................................................................51
5.3.2 Message Sample Id Announcement................................................53
5.3.3 Message IPC Result..........................................................................55
5.4 Warehouse................................................................................................. 56
5.4.1 Message Incoming Transport...........................................................56
5.4.2 Message Outgoing Transport...........................................................58
5.4.3 Message Permanent Inventory.........................................................60
5.4.4 Message Inventory Reconciliation...................................................62
5.5 Detailed Scheduling..................................................................................63
5.5.1 Message Process Order...................................................................63
5.6 Production Execution...............................................................................68
5.6.1 Status Data........................................................................................ 68
[Link] Message Start Manufacturing Order........................................68
[Link] Message Performance Data of Shop Floor Order...................69
[Link] Message Abort Manufacturing Order......................................70
[Link] Message End Manufacturing Order.........................................72
[Link] Message Group Leader Approval for Manufacturing Order. .73
[Link] Message Production Pharmacist Approval for Manufacturing Order 75
[Link] Message Quality Assurance Approval for Manufacturing Order 76
5.6.2 Stock Data.......................................................................................... 78
[Link] Message Take Out on Manufacturing Order...........................78
[Link] Message Stock Creation on Manufacturing Order.................79

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 6 of 61
 List of Figures

Fig. 1: Principle of data exchange (general)..................................................................9

Fig. 2: Principle of data exchange (detail)....................................................................10
Fig. 3: Interface & booking logic...................................................................................11
Fig. 4: Business processes and data communication for master data.....................14
Fig. 5: Recipes in SAP and PAS-X................................................................................16
Fig. 6: Business processes and data communication for quality check of batches 18
Fig. 7: Batch status........................................................................................................ 19
Fig. 8: Use of potency in BOM and batch data.............................................................19
Fig. 9: Business cases and data communication for scheduling..............................21
Fig. 10: Business cases and data communication for preparation of production....23
Fig. 11: Business cases and data communication in execution................................25
Fig. 12: Business cases and data communication for warehouse management......28
Fig. 13: Storage areas in SAP and in PAS-X................................................................29
Fig. 14: Storages in SAP (storage types) and in PAS-X (WMS locations) - I.............30
Fig. 15: Storages in SAP and in PAS-X - II...................................................................30
Fig. 16: Data communication for changes in storage locations.................................31
Fig. 17: Inventory location identification......................................................................32
Fig. 18: Identification & Link between pallet, load, and storage unit.........................33
Fig. 19: Material staging................................................................................................. 34
Fig. 20: Return to stock.................................................................................................. 35
Fig. 21: Stock movement............................................................................................... 35
Fig. 22: Inventory adjustment........................................................................................36
Fig. 23: Inventory reconciliation....................................................................................37
Fig. 24: PAS-X interface and involved interface layers using IDocs via XML...........38
Fig. 25 Messages involved in the SAP interface..........................................................47

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 7 of 61
1 Enterprise Resources Planning Interface

1.1 General Design & Business Processes

The illustrations and explanations below will help to understand the interface.
The details are intended to
 outline the activities and responsibilities for each system,
 define the business processes relevant for the interface,
 define the messages to be sent (associated with the business process),
 provide background information about the data needed in the messages

Fig. 1: Principle of data exchange (general)

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 8 of 61
 Fig. 2: Principle of data exchange (detail)

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 9 of 61
Interface & booking logic
The controlling indicators, such as the movement type, and the sequence of required item
records are derived from the user's actions and the used application.
An interface transfers the data of a business case irrespective of the receiving system's booking
logic. Thus, there are no effects on the interface or on the sending system if the booking logic of
the receiving system should change.
The messages sent from this PAS-X interface to SAP may result in several booking steps to be
done in SAP.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 10 of 61
The following terms are used:
 Systems
The term ‘system’ is used to describe the communication partner:
 SAP
for the SAP system
 PAS-X
for the MES
 LIMS
for the LIMS system
 Storage location (location and type)
The warehouse management component is generally able to distinguish the systems
primarily managing the storage location.
For reasons of clearness, all SAP storage locations (storage location and storage type) are
summarized by the terms:
 "SAP"
for all storage locations and storage types managed in SAP (stock not known in
PAS-X)
 "PAS"
for all storage locations and storage types managed in PAS-X (stock is known in
SAP, either)
 Production
Global term to summarize all kinds of manufacturing orders e.g.: bulk production, packaging
 Business case
The business case is at the top of the hierarchy of structured user activities. The name of a
business case stands for a series of associated user actions carried out one after the other.
One or several messages are created while executing the user actions of a business case.
 Message
Term used to describe the data communication for a specific type of data on a general basis.
The term ‘message’ may usually be considered as synonym for the term ‘telegram’. One
message, though, may consist of several telegrams.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 11 of 61
1.1.1Master data
In order to provide the intended support in the process flow of production, the systems need to
populated with extensive master data. There are different major types of master data to be
communicated between the systems.

Fig. 3: Business processes and data communication for master data

Resource Master Data

Resource master data require different designs (modeling) in SAP and PAS-X.
Moreover, in terms of data not all the resources are required in both systems. For this reason, all
resource data is separately (redundantly) maintained in the two systems.
Resources may be summarized into a resource group.
There is an SOP to ensure that the resource identifications used in the two systems are named
the same (e.g. production units, classification types of personnel, scales, set-up parts).

[Link] Material Master Data

Data maintenance in SAP

New material master data can be created and existing data is maintained in SAP. New or
changed material master data is transferred to PAS-X. The triggering point is by means of the
SAP change pointer, however it can be triggered manually (BD10). The data transferred states
new entries, changes, and deletions (deletion flag set).

Extending data in PAS-X

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 12 of 61
In the MES, information aspects relevant to quality, production, standard potency, and safety are
added to complete the data. Since such data is exclusively used in the MES, the added
information is not reported back to the SAP system. The SAP system does not perform any base
data modifications that would affect the added data.

Releasing data in PAS-X

New material master will be created in status ‘New from SAP’ in PAS-X if the automatic release
indicator is not set. These material master data need to be acknowledged manually in PAS-X
after supplementary data such as R&S phrases has been added. Updates of the material master
will not change the release state except for deletions. New material master will be acknowledged
automatically if the release indicator is set, no manual release step is required.

<<Rama Comments 23 May 2022>>

OPTION II: (to review based on business comments)

New material master will be created in status ‘New from SAP’ in PAS-X.
The release of Material Status in PAS-X (after the creation in SAP) will be done manually by the
business in real time.
These material master data need to be acknowledged manually in PAS-X after supplementary
data such as R&S phrases has been added. Updates of the material master will not change the
release state except for deletions.

[Link] Master Recipe (BOM & Routing)

The master recipe is created and maintained in SAP. Associated with the master recipe are
operations and phases to describe the process briefly for business purpose and a part list of
material necessary to perform the given process. Both master recipe and BOM are linked
together by a production version.
Very similar, the Master Batch Record (MBR) is created manually and maintained in PAS-X.
Associated with the Master Batch Record are basic operations as well as BOMs related to the
basic operations and basic functions. The MBR defines the process more precisely and with all
aspects concerning with pharmaceutical GMP aspects.
Subsequently the term “Recipe” is used to describe both the Master Batch Record (MBR) in
PAS-X and master recipe, BOM and production version in SAP.

<<Rama Comments 23 May 2022>> Should be

Very similar, the Production Version (linked with both Master recipe and BOM) is transferred
from SAP to PAS-X inform of Master Batch Record (MBR) and maintained in PAS-X.

Production versions from SAP are transferred to PASX in form of MBR – right?

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 13 of 61
 Fig. 4: Recipes in SAP and PAS-X

In both systems the following indications are used for unique identification of master
recipe/MBR:
 Material number
 Recipe version (def. in SAP technical specification) in SAP and production version in MES.
(The term recipe version is used as Astellas currently does not use production versions.
However, SAP ensures to send a recipe version which is alike to a production version from a
MES point of view.)

Recipe Synchronization

SAP is the leading system for creating and changing recipes. The data in SAP are focused on
commercial and planning aspects. Based on the information from SAP the pharmaceutical re-
finements are added in PAS-X. The approval period for packaging is 14 calendar days and 30
calendar days for others.
Recipes are transferred to the MES, where they are entered into a reception buffer. Changes
made to recipes already existing in the MES will be ignored. The MES user decides on the
method to be used for transferring the recipes into the MBR structures. Possible methods to load
the data from the reception buffer are:
 Create a new MBR
 Create a new MBR version
 Create a new parameter value list and a new parameterized MBR based on an existing
generic MBR

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 14 of 61
  Create a new version of a parameter value list and a parameterized MBR based on an
existing generic MBR
BOM items of type ‘text item’ e.g. demi water not transferred to PAS-X. These items are added
manually when refining the MBR in PAS-X. These items are treated as non SAP relevant. Order
related consumptions of these items will not be reported to EBR.
Other ‘non-stock items’ e.g. clichés (material type ‘NLAG’) for which PAS-X will not do
consumption postings will be sent to PAS-X but the affected material master will be flagged as
non-consumption relevant for SAP. This flag will be set as a characteristic on the material
master.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 15 of 61
1.1.2 Quality Assurance
For all batches SAP defines and maintains the batch status and associated batch data, such as
expiration date. The actual potency is maintained in LIMS but send through SAP to MES.
The initial batch status is defined by the material master data. Within the material master data
SAP sends the initial batch status value to PAS-X. This information is used in PAS-X to set the
initial batch status for the material produced by the manufacturing order.
Based on sampling ids generated in LIMS sampling for produced batches is done in PAS-X. The
corresponding IPC results are moved back to LIMS.

Fig. 5: Business processes and data communication for quality check of batches

[Link] Batch Master

Batch status and batch data are processed in SAP.
All new batches and batch data changes which are relevant for PAS-X are moved into PAS-X
dynamically. Changes are sent immediately.
Due to the fact that not all SAP storage locations are known/administered in PAS-X, it may
happen that still no stock is known in PAS-X for the batch information transferred. PAS-X
however accepts all batch information, irrespective of current stocks.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 16 of 61
Three different batch status values are possible:

Fig. 6: Batch status

Only batches that are free for unrestricted use (status “released - unrestricted”) or batches that
are free with conditions (status “released - restricted stock”) can be used for a manufacturing
order. Therefore SAP maps the batch status applied in SAP into the batch status needed in
PAS-X (restricted stock or unrestricted).
SAP administers the status of a batch separately for the individual quantity in each storage
location.
PAS-X administers the status of a batch for the whole quantity in all storage locations.
There is a standard operating procedure (SOP) in SAP to make sure that the change of a batch
status in SAP is always done for all quantities in all storage types, respectively only materials
having a batch status that is known in MES will enter the production.

Batch Potency
Batch potency for active ingredients is processed in LIMS and published to SAP. Each time the
potency for a batch related to PAS-X is determined or changed, the current potency is reported
to PAS-X by SAP if the material is flagged as ‘relevant to calculation’ in SAPs material master. If
the flag is not set, the standard potency will be sent as actual potency.

Active ingredients and consideration of their different potencies

Active ingredient data is needed in the weighing process to adjust the BOM quantities.

Fig. 7: Use of potency in BOM and batch data

The concept to handle the different potencies of each batch within this interface is as follows:
 Standard potency (100 %) in BOM
The quantity in the BOM is based on a “standard” potency; for easy use it is defined as
100 %. This is true for all materials which are active ingredients and the fixing is not
communicated from SAP to PAS-X (e.g. within the material master).
 Current potency (x %) in batch data
Within the batch data SAP sends a factor to PAS-X for correcting the quantities of the BOM in
PAS-X. For easy use, this value is also defined in %. 90 %, for instance, means that the

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 17 of 61
 batch has only 90 % of the potency assumed in the BOM. Therefore, the batch quantity to be
weighed out must be increased accordingly. An indication of 110 % means that the batch
quantity must be decreased.
This is also applicable for material which is not active but having potency.
All values relating to potencies (standard and actual potency as well as resulting percentage
values for correction) are defined by QA and entered into SAP or LIMS.

Check batches for admissibility prior to use in production

The batch information is not available and complete from the beginning. Various pieces of
information may be supplied step by step and distributed onto several telegrams sent by SAP. In
case not all batch data information is available PAS-X performs two verification operations to
ensure that no batch can be used within production.
 Change of batch status to ‘release’
If the batch status is going to ‘release’ within the batch data message, the change of the
status will only be done, if all values are well defined. If e.g. the actual potency is still missing
and the material is an active ingredient, the check will fail and the message results in an error
status within the interface.
 Batch data for material staging message
The creation of inventory based on the material staging message from SAP will fail, if the
corresponding batch master data is not already known in PAS-X

[Link] Sample Id Announcement

In order to perform sampling operations as well as to enable sample label print in PAS-X, LIMS
creates sample ids (one per configured sample step) for each process order which is transferred
to PAS-X. Based upon this sample ids, quality control operations are performed in PAS-X for the
concerning manufacturing order. The release of the process order in SAP triggers the sample id
generation in LIMS. LIMS sends the generated samples ids to PAS-X right away.
One sample id is generated for the sample steps (e.g. IPC, chemical/physical, micro biological,
retain sample, etc.).

[Link] IPC Result

Quality control operations for produced batches are done in PAS-X based on a sample id
received from LIMS. The acquired IPC results (time and labor data) are reported to LIMS after
the group leader approval is done in PAS-X.
Results are captured via activities of type measured value. Element-markers assigned during
MBR creation mark the activity as LIMS relevant and define values of method code, component
code, replicate no, unit of measure of result and sample step.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 18 of 61
1.1.3 Scheduling
The processes of scheduling production and planning material resources are executed in SAP.
PAS-X accepts the received process orders as manufacturing orders.

Fig. 8: Business cases and data communication for scheduling

[Link] Process Orders

As soon as a process orders is released in SAP the order header data including the recipe
version and optional batch allocations for input material are transferred to PAS-X.
On the basis of the process order data received from SAP, a manufacturing order is created in
PAS-X. The status of this order is set to ‘release manufacturing control’ (RMC).
Before starting the order in PAS-X all changes by SAP will be accepted. Afterwards, the order is
closed for modifications by SAP.
Within PAS-X the scheduled times and the order quantity might also be changed. These
changes are not reported back to SAP.
The process order is linked to the MBR using SAPs recipe version.

Target batch number

The target batch number is defined in SAP and reported to PAS-X within the process order
message.

Specification of Batches to be Used

Allocations of input batches are made in SAP. The existence of allocations is optional to PAS-X.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 19 of 61
1.1.4 Preparation
Various preparations take place after completion of production scheduling and prior to starting
actual production.

Fig. 9: Business cases and data communication for preparation of production

Material staging for production

A central task within the scope of preparing production is the staging of material. There are 2
steps:
 General material supply by SAP
SAP manages the supply of material to storage locations administered by PAS-X. On the
basis of customer order, planned orders, process orders,
– SAP orders material from the vendors and
– SAP initializes the transport into PAS-X
to stock up the PAS-X storage locations
 Material staging for production unit by PAS-X
PAS-X manages the material flow to the production units. The user in PAS-X is informed
about stocks available in the production supply area (PSA) and about the demands for
manufacturing orders. To stage material, the user in PAS-X may use the normal PAS-X
transport functionality.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 20 of 61
Update Process Order
The user in PAS-X is able to change the scheduled dates and the quantity of an order. These
changes are not reported back to SAP.

Release of Manufacturing Order

After finishing production preparation-steps the order will be released in PAS-X for
manufacturing (status RMC). SAP is not informed about the release of the corresponding
process order.

<<Rama – to review and updated after acceptance>> 23 May 2022

After finishing production preparation-steps the order will be released in SAP and the release is
transferred to PAS-X for manufacturing (status RMC). An early batch number would be
generated for the Process order in SAP, the generated batch number and other parameters
would be transferred to PAS-X

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 21 of 61
1.1.5 Execution
All production activities relevant in manufacturing are reported to SAP.

Fig. 10: Business cases and data communication in execution

[Link] Start of Manufacturing Order

The start of production (start of first shop floor order will start the manufacturing order) is
reported to SAP in order to set the actual start date of the concerning process order and to
trigger the material staging process. The order will be closed for modifications.

Interruption / continuation of a PAS-X shop floor order

In case of production malfunctions the shop floor order can be interrupted and be resumed after
clarification or removal of the problem. These changes are not reported to SAP.

Changing a PAS-X shop floor order

Should it be necessary to adapt to a new production situation, the shop floor order can be
changed appropriately. This kind of change is not reported to SAP either.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 22 of 61
[Link] Performance Data of Shop Floor Order
After each shift the machine times as well as personnel times for cost accounting purposes are
acquired and accumulated per shop floor order in PAS-X. The data is acquired using a specific
basic function with activities of type measured value.
Upon end of a shop floor order these times are transmitted to SAP.

[Link] Take out on Manufacturing Order

Consumption values are acquired in PAS-X. The data will be forwarded to SAP with reference to
the process order.
In order to correct already reported material consumptions, cancellation messages will be used.
The posting of material consumptions is always related to both the order and the inventory level.

[Link] Stock Creation on Manufacturing Order

PAS-X acquires the materials (bulk, finished goods) produced and forwards the data to SAP with
reference to the SAP process order.
In SAP, a material goods receipt has to be posted for the order. The inventory level is adjusted
automatically.
Cancellations of stock creations are not sent to SAP. However, this interface can be activated by
setting an appropriate configuration in the distribution model of PAS-X interface layer.

[Link] End of Manufacturing Order

After completion of all activities a manufacturing order will be finished in PAS-X.
The completion of the manufacturing order will be reported to SAP in order to set the actual end
date of the concerning process order as well as the status ‘technical completed’ (TECO).

[Link] Abortion of Manufacturing Order

In case of an emergency, the manufacturing order can be aborted in PAS-X.
SAP will automatically get according information.
The abortion message replaces the normal “completed/finishing” message for a manufacturing
order.
Such an abortion may take place at the beginning or also at the end of production (i.e. before
and after consumption or addition messages).
Three different scenarios apply:
1) After Order is released but before order is started
a) Abort Order in SAP
b) Status sent to EBR by Interface
c) Delete Order in PAS-X
2) After Order is Started but before goods are issued/consumed
a) Abort order in EBR  Order updated in SAP by Interface ( TECO, GLA, PPA,
GCA ) and order quantity = 1
3) After Order is Started after goods are issued/consumed
a) Cancel goods issued where possible in EBR
Version: V0.1 - Date of this version: 24-06- 2022
Document name: PAS-X-SAP Interface
Page 23 of 61
 b) Interface to SAP to perform reversal of issue (262)
c) Perform “Push out ” Transaction in EBR creating by interface, a transfer
requirement in SAP then move to WHS with Transfer order
d) GOTO option 2

In SAP the end date of the concerning process order will bet set.

[Link] EBR Approval Status

If subsequent approvals are done in PAS-X an appropriate message is created in order to set
the corresponding user status of the referenced process order in SAP.
 Group leader approval  status ‘GLA’
 Productive pharmacist approval  ‘PPA’
If subsequent approval is done in PAS-X an appropriate message is created in order to set the
corresponding status to the batch record in LIMS.
 Quality assurance approval  ‘QAA’

Group leader approval status is not send to SAP, because this interface is not implemented on
SAP site yet. However, this interface can be activated by setting an appropriate configuration in
PAS-X.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 24 of 61
2Technical Design

2.1 Interface Layers

Communication from PAS-X is made in two layers:
 The actual interface (providing different technologies) for direct communication with SAP and
 An interface layer that provides data to the application in standardized form or collects data
from the application.

The diagram below shows the basic procedures and the components involved in the
communication process:

Fig. 11: PAS-X interface and involved interface layers using IDocs via XML

For the communication between PAS-X and the LIMS system PI is utilized as well.

2.2 Interface Technology

Since the inbound and outbound messages are always buffered in the MES interface layer the
message transfer on MES site is always decoupled from the application regardless of the
interface technology deployed.
This ensures that the MES application is always able to continue its task even if the SAP or
actually the interface is not available.
Version: V0.1 - Date of this version: 24-06- 2022
Document name: PAS-X-SAP Interface
Page 25 of 61
The communication is message oriented. Each processing of a business case which is
designated to be exchanged activates the creation of a message. Each message consists of a
header record and one or more data records which hold the actual business case data. Each
business case is represented by different message types. Depending of the message type
different structures and the dedicated processing will be recognized.

2.3Restart Behavior
The interface processes of MES have an auto-restart function. So, when starting the computer
or if a process fails automatic restart can be configured, if required.
A loss of data is impossible as the telegrams not yet transferred to SAP and the telegrams not
yet entered into the MES application database are saved into buffer storage.

2.4 Error Handling

2.4.1 System Behavior

Communication between sender’s output and receiver’s input is not handled as transaction. For
this reason, special measures are required to ensure data consistency.
The sender of a message ensures the message is placed securely into the interface layer. The
sender’s interface functionality executes a plausibility check for the communication leaving. In
case of any errors, the sender treats them internally. No data is sent.
The receiver of a message processes the data independent of the sender. The receiver’s
interface functionality carries out a plausibility check for the data communicated. In case of any
errors during input processing, the receiver treats them internally. There is no callback to the
sender. No feedback message is sent to the sender.

2.4.2 User Behavior

Should the results of plausibility checks in MES show discrepancies in the contents of telegrams
in the input processing or should it not be possible to send a telegram to SAP, the telegram
remains in MES interface layer. An according error status indicates that an error was
recognized.
The user can choose between two alternatives:
 Retriggering the telegram processing in MES
after the problem is eliminated input processing or communication to SAP can be triggered
again.
 Deleting the telegram
the user can delete the telegram in MES. After it was deleted, however, the user must
manually take care of appropriate data consistency in MES as well as in SAP.

2.5 General Conditions

The general conditions stated below apply to the entire data communication:

 Messages are communicated to SAP only once

(even if several SAP components are concerned)
The data is communicated between the systems SAP and MES, not between single
components of the two systems. The business case data is communicated to the partner

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 26 of 61
 system only once. If it is necessary to forward the data inside the receiving system (e.g. from
process order control to warehousing), the transfer is made as system internal transfer only.

 No reference in messages to previous SAP operations/documents

Any booking operations with reference to previous SAP operations/documents are carried out
in SAP only.

 No negative stock
MES does not report any withdrawal quantities to SAP that are not covered by the stocks
available in MES. If necessary, MES first sends an inventory adjustment message to SAP.

 Chronologically correct order

The data to be communicated are subject to a chronological order. The sending system
makes sure that the data is communicated in correct chronological order. The receiving
system has to process the data in the order they were sent.
To define a clear chronological order for telegrams the series flag is set in the IDoc control
record in the following format:
standard date + standard time + tenth of a second + hundredth of a second
MES takes the indications from the operating system of the server. Thus, the chronological
order still is correct (distinctive) even if several telegrams should be created within the scope
of one business case.

Extract
The IDoc telegram structures stated on the pages below do not include all the IDoc fields, but
are restricted to the relevant environment. The telegram structures serve to illustrate the fields
that are processed/ provided in the message.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 27 of 61
3 Data Formats
According to the SAP standard, user data are transferred over the interface in CHAR format
(character) only.
Data type Short Format
Date DATE YYYYMMDD
Time TIME HHMMSS
Numerical value NUMC n n numerical characters, unsigned with leading
zeros
Example:
format NUMC 4 - value 88 is 0088
The total field length is 4 characters.
Integer value NUM n Integer with n numerical characters, unsigned
Example:
format NUM 4 - value 88 is 88
The total field length is 4 characters.
Decimal value NUM n,m Decimal value with n numerical characters
before decimal point, m numerical characters
after decimal point and one wild-card for sign
at first position
Example:
format NUM 3,2 - value 122,45
The total field length is 7 characters (1 Blank +
3 characters before decimal point + 1 decimal
point + 2 characters after decimal point)
Alphanumerical values CHAR n alphanumerical characters. Pure values are
transmitted. Leading zeros and blanks are not
added.
The following data lengths and field semantics have been agreed:
Field Processing
Material number In the application the material number has a max length of 18 characters.
SAP to PAS-X:
Material numbers are taken over without leading zeros. Only numerical material
numbers exist.
PAS-X to SAP:
Material numbers are reported with leading zeros as they were submitted.
Manufacturing order In the application the manufacturing order number has the max. length of
number 12 numerical characters
SAP to PAS-X:
Leading zeros transferred by SAP are completely eliminated in PAS-X.
PAS-X to SAP:
PAS-X adds leading zeros.
Batch number In the application the batch number has the length of max. 10 characters.
Item number SAP to PAS-X:
Item numbers are taken over as they are received.
PAS-X to SAP:
Item numbers are reported unchanged.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 28 of 61
Changes made on the number range objects in SAP effect the interface. If number ranges are
put into the interface layer that differs from the agreed data element length, errors will occur
since it is no longer possible to communicate and process the data properly.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 29 of 61
4 Message Structure
The interface uses a number of data structures to handle the communication for relevant
business cases.
The various data structures are used for the different business cases.
All the data structures are described as follows:
 The data structure will be explained from the application's point of view, i.e. only the data
relevant for the receiving system's application will be stated.
 Only formats the data of which are required/ processed by the application will be stated.

Legend for the tables in the following chapters

Structure
To be defined

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 30 of 61
5 Message Content
The tables in the chapters below describe the usage of the data structures within the messages
(business process).

Legend for the tables in the following chapters:

Telegram structure
Before the actual description of the telegram structure there first is an overview of the message
type and the segments used containing the following information:
Message type
Message variant
Segment
The following symbols are used:
 The statement exists in all business processes and variants
optional The statement exists in the business process or variant only on certain conditions
--- The statement does not exist in any of the business processes or variants
To point out whether a telegram structure contains header as well as item data and to illustrate
the hierarchical structure the segment names are indented in the overview. If data of the same
level is just distributed to several segments, the segment names are not indented.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 31 of 61
5.1 Overview

Depending of the distribution of responsibilities several demands for data exchange occurs. The
following picture gives an overview about the message flow provided by the SAP interface:

Fig. 12 Messages involved in the SAP interface.

5.2 Master Data

5.2.1 Message Material Master Data

Interface Trigger Telegram Remark

Message ID
Creation Updat Cancel Num Direc
e ber tion
by change
SAP
IF_SAP_ pointer or All materials relevant to PAS-X are known in
Y Y 1 
MaterialData triggered SAP and MES alike.
MES
manually

General conditions
 All materials received from SAP regardless any filter settings are stored into a buffer table.
 Material master data is not transferred in lists, but each material master data record creates a
telegram of its own.
 Message for newly created material master data do not require all segments stated below.
These messages will be rejected as long as not all MES mandatory fields are included.
 When material master data was changed, all segments are transferred, not only the ones that
were changed.
Version: V0.1 - Date of this version: 24-06- 2022
Document name: PAS-X-SAP Interface
Page 32 of 61
  Changes not related to MES relevant data will not be taken over into MES.
 Material master data updates from SAP will not change the MES release status.
 Standard bundle size will be defined as conversion factor for alternative unit of measures
(either conversion factor for piece/carton or kilogram/drum).
 Active ingredient indicator is maintained in SAP and reported to PAS-X.
 Alternative unit of measures and appropriate conversion factors are maintained in SAP and
reported to PAS-X.
 R&S phrases are maintained in MES and linked to the material master data in PAS-X
manually.
 Newly created material master (automatic release indicator not set) must be extended in MES
and acknowledged manually before it can be used in MES.

Overview of message variants and segments used

Message type
Message variant: ---
MATMAS
Segment
E1MARAM 
Segment
E1MAKTM 
Segment
E1MARCM 
Segment
E1MARMM
optional
Segment
ZAUSP_ MES optional

Overview from telegram point of view

Telegram information Data information
Basic type: ZMATMAS05
Extension: --- Initial Update Deletion (flag)
Sending system only telegrams with data relating to the site
Filter telegram only telegrams with data relating to MES
Receiving system
(based on a user defined filter)
1 telegram
Number of telegrams in business process
(per material number)
Segment information
Structure: E1MARAM
Definition: E2MARAM006
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
MATNR – CHAR 18 Material number
MTART – CHAR 4 Material type
(optional)
MEINS – CHAR 3 Basic unit of measure in ISO code
Gross weight
BRGEW – NUM 10,3
(optional)
Net weight
NTGEW – NUM 10,3
(optional)

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 33 of 61
 Telegram information Data information
Basic type: ZMATMAS05
Extension: --- Initial Update Deletion (flag)
Weight unit (gross/ net weight)
GEWEI – CHAR 3
(optional, mandatory if gross/ net weight is set)
Total shelf life
MHDHB – NUM 6
(optional)
Unit for shelf life
(optional, mandatory if shelf life is set):
’D’ – day
IPRKZ – CHAR 1
‘W’ – week
‘M’ – month
‘Y’ – year
External material group
EXTWG – CHAR 18
(optional)
PRDHA – CHAR 18 Product hierarchy
Segment information
Structure: E1MAKTM
Definition: E2MAKTM001
Sending system only segments with English language
Filter segment
Receiving system not required
Number of segment records 3 segment record
Field information
MSGFN - CHAR 3 Text type
“MDT” – Material description (makt-maktx (mandatory))
“BDT” – Basic data text (text-id GRUN (optional))
“MGD” – Material group description (t023t-wgbez60 (optional))
MAKTX - CHAR 40 Material description
Segment information
Structure: E1MARCM
Definition: E2MARCM004
Sending system only segment relating to the MES plant
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
WERKS – CHAR 4 Plant
(constant value)
INSMK – CHAR 1 Subject to quality control indicator:
“X” (default batch status = quarantine )
otherwise:
default batch status = released
XCHPF – CHAR 1 Requiring batch handling indicator:
“X" if material requires batch handling,
otherwise: blank
LVORM – CHAR 1 „X“
(material master data
--- ---
should be marked as
deleted)
MARC- AUSME Unit of Issue (work scheduling view)

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 34 of 61
 Telegram information Data information
Basic type: ZMATMAS05
Extension: --- Initial Update Deletion (flag)
Segment information
Structure: E1MARMM
Definition: E2MARMM003
Sending system not required
Filter segment
Receiving system only segments with data relating to MES
n segment records
Number of segment records
(per alternative unit of measure)
Field information
MEINH – CHAR 3 Alternative unit of measure in ISO code
UMREZ – NUM 5 Numerator for conversion to base units of measure
UMREN – NUM 5 Denominator for conversion to base units of measure
Segment information
Structure: ZAUSP_MES
Definition: ZAUSP_MES000
Sending system not required
Filter segment
Receiving system only segments with data relating to MES
n segment records
Number of segment records
(per characteristic)
Field information
ATNAM – CHAR 30 Characteristic name
Characteristic value
ATWRT – CHAR 30
(see overview of characteristics used in segment below)

Overview of characteristics used in segment ZAUSP_MES

Characteristic name Description Format Comment
STANDARD_POTENCY Standard potency NUM 7,1 Optional, mandatory if
material is active ingredient.
(Default 100 transmitted)
STANDARD_POTENCY _UOM Standard potency unit in CHAR 3 Optional, mandatory if
ISO code material is active ingredient.
(Default PCT transmitted)
MES_MATERIAL_TYPE MES material type CHAR 1 0 – Raw material
1 – Active ingredient
AUTOMATIC_RELEASE Automatic release CHAR 1 “ “ – no release
indicator “X” – automatic release
HAZARDOUS_UN_CODE Hazardous UN code CHAR 6 Optional
TEMP_CONDITION_DESC Temperature condition CHAR 20 Optional
description
EXT_MAT_GROUP_DESC External material group CHAR 20 Optional
description
CONSUMPTION_RELEVANT Whether consumption CHAR 1 “X” – consumption relevant
messages will be posted “ “ – not relevant
for that material.

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_MaterialD Material Master Message
ata The data received is integrated into the material master of MES. Primary, a material
Version: V0.1 - Date of this version: 24-06- 2022
Document name: PAS-X-SAP Interface
Page 35 of 61
 Interface Brief Description
Message ID Description
(Change Flag)
(C) master record will be inserted into buffer tables. If the data already exists there the
concerning entry will be updated. If either an entry for the received material master
data exists already in the MES destination tables or if it was a new entry into the
buffer tables, the material master record is taken over into the MES destination
tables. Otherwise it will stay unprocessed in the buffer.
Depending on the automatic release indicator (indicator is not set) the received data
gets the status 'New from SAP'. Using this option, the user is informed whether the
data received has to be supplemented and acknowledged. Otherwise (indicator is
set) the material master will be acknowledged automatically.
Updates of the material master data will not change this release status anymore.
Material records with a deletion flag get the corresponding status 'Deleted by SAP'
in MES.
Audit trail information is generated to indicate the changes.

5.2.2 Message Master Recipe (BOM & Routing)

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
Received data are stored into an
triggered SAP
intermediate buffer. Taken-over from this
IF_SAP_Recipe automatically Y Y 1 
buffer into MES is done in part manually or
within posting MES
dynamically.

General conditions
 The SAP production scheduler will be mapped to the MES production area.
 Only released recipe versions (in SAP status: 4 released general) are transmitted.
 Each change related to MES data will cause a new recipe version in SAP.
 SAP internal operations/phases are not transmitted (only production operations/phases).
 Alternative resources (production units) are not transmitted.
 The completion of the master batch record (MBR) and the pharmaceutical approval workflow
are done in PAS-X.
 Only the valid-to date may be updated and the valid-from date in case valid-from is still in the
future.

Overview of message variants and segments used

Message type
Message variant: ---
ZMASRCP
Segment
ZMKAL_H 
Segment
ZPLKO_H 
Segment
ZSTPO_H optional

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 36 of 61
 Message type
Message variant: ---
ZMASRCP
Segment
ZPLPO_H optional
Segment
ZPLMZ_I optional

Overview from telegram point of view

Telegram information Data information
Basic type: ZMASRCP01
Extension: --- Initial Deletion (flag)
Sending system only telegrams with data relating to the site
Filter telegram
Receiving system only telegrams with data relating to MES
1 telegram
Number of telegrams in business process
(per recipe version)
Segment information
Structure: ZMKAL_H
Definition: ZMKAL_H000
Sending system only segments with production version relating to MES
Filter segment
Receiving system only segments with data relating to MES
Number of segment records 1 segment record
Field information
Plant
WERKS – CHAR 4
(constant value)
MATNR – CHAR 18 Target material number
VERID – CHAR 4 SAP recipe version
Production scheduler
FEVOR – CHAR 3
(optional)
Short text on the recipe version
AETXT – CHAR 40
(optional)
MKSP – CHAR 1 --- ‘X’
Lower value of the lot-size
BSTMI – NUM 10,3
(optional)
Upper value of the lot-size
BSTMA – NUM 10,3
(optional)
ADATU – DATE Valid-from date (inclusive)
BDATU – DATE Valid-to date (inclusive)
Group Counter/recipe id
PLNAL – CHAR 2
(optional)
Alternative BOM
STLAL – CHAR 2
(optional)
Segment information
Structure: ZPLKO_H
Definition: ZPLKO_H000
Sending system only segments with recipe data relating to MES
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
BMSCH – NUM 11,3 Base quantity
Unit of measure in ISO code
MEINH – CHAR 3
for base quantity and lot-size

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 37 of 61
 Telegram information Data information
Basic type: ZMASRCP01
Extension: --- Initial Deletion (flag)
Segment information
Structure: ZSTPO_H
Definition: ZSTPO_H000
Sending system only segments with BOM item data relating to MES
Filter segment
Receiving system not required
n segment records
Number of segment records
(per BOM item)
Field information
POSNR – NUMC 4 BOM item number
IDNRK – CHAR 18 BOM component
Item category:
2 – leading component
L – stock material
POSTP – CHAR 1
1 – auxiliary material/consumables
Z – additional item for text
X – order specific text
MENGE – NUM 11,3 Component quantity
MEINS – CHAR 3 Component unit of measure in ISO code
Alternative item: group
ALPGR – CHAR 2
(optional, only mandatory if alternatives exist)
Usage probability in %
EWAHR – NUM 3
(optional, only mandatory if alternatives exist)
Segment information
Structure: ZPLPO_H
Definition: ZPLPO_H000
Sending system only segments with operation/phase data relating to MES
Filter segment
Receiving system not required
1 n segment records
Number of segment records
(one per phase/operation)
Field information
VORNR – CHAR 4 Operation / activity number
PHFLG – CHAR 1 Indicator: phase
Superior operation
PVZNR – CHAR 4
(optional if phase indicator is not set)
ARBPL – CHAR 8 Work center
Operation short text
LTXA1 – CHAR 40
(optional if phase indicator is set)
Segment information
Structure: ZPLMZ_I ---
Definition: ZPLMZ_I000
Sending system only segments with BOM item data relating to MES
Filter segment
Receiving system not required
n segment records
Number of segment records
(per BOM item)
Field information
POSNR – NUMC 4 BOM item number
VORNR – CHAR 4 SAP Phase number

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 38 of 61
 Interface Brief Description
Message ID Description
(Change Flag)
IF_SAP_Recipe Master Recipe Message
(C) The Master Recipe data received from SAP is integrated into an intermediate buffer
in MES. This buffer serves as a template for a qualified person in MES in order to
update the MBR in MES accordingly.
Should the data in the buffer already exist only valid-to and possibly valid-from will
be updated if valid from is still in the future.
In general, the status of an existing MBR will not be changed dynamically. It lies
always in the responsibility of the qualified person in MES to carry out any status
transition. The only attribute that is update is the valid-to date. If the date is
changed, all affected master batch records are update automatically.
Audit trail information is generated to indicate the changes.

5.3 Quality Control

5.3.1 Message Batch Data

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered SAP
IF_SAP_BatchDat
automatically Y --- 1 
a
within posting MES

General conditions
 Batch data is maintained in SAP.
 Batch data are transferred to MES regardless the existence of inventory.
 SAP administers the status of a batch as inventory type, i.e. separately for the individual
stock quantities in each storage type.
 MES administers the status of a batch as a master date, i.e. always for the whole quantity of
a batch, independent of the stock quantities in the individual storage locations.
 Therefore, an SOP is necessary to fix that the change of a batch status in SAP is always
done for all quantities in all storage locations, respectively only materials having a batch
status that is known in MES will enter the production.
 If the batch status designates a batch as released all mandatory batch attributes must be
specified (i.e. actual potency in case of active ingredients).
 If the material number is not known in MES the message will fail.
 The unit of measure for the actual potency must match with the unit of measure for standard
potency within the material master. Otherwise the message will fail.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 39 of 61
Overview of message variants and segments used
Message type
Message variant: ---
ZBATMAS_EBR
Segment
E1BATMAS 
Segment
E1BPBATCHATT 
Segment
E1BP3060_VALUATION_CHAR
optional

Overview from telegram point of view

Telegram information
Basic type: BATMAS03 Data information
extension: ---
Sending system only telegrams with data relating to PAS-X
Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business case
(per batch)
Segment information
Structure: E1BATMAS
Definition: E2BATMAS000
Sending system only segment records relating to PAS-X
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
MATERIAL –CHAR 18 Material number
BATCH – CHAR 10 Batch number
PLANT – CHAR 4 Plant
“NL01”
Segment information
Structure: E1BPBATCHATT
Definition: E2BPBATCHATT000
Sending system only segment records relating to PAS-X
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
EXPIRYDATE – DATE Expiration date
(optional; mandatory if batch status is free)
PROD_DATE – DATE Manufacturing date
(optional)
STATUSKEY – CHAR 1 Status for the whole quantity in all storage locations:
"F" (Unrestricted - Free)
“R” (Restricted – Free with conditions)
"S" (Blocked)
"X" (Quarantine)

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 40 of 61
 Telegram information
Basic type: BATMAS03 Data information
extension: ---
Segment information
Structure: E1BP3060_VALUATION_CHAR
Definition: E1BP3060_VALUATION_CHAR
000
Sending system not required
Filter segment
Receiving system not required
Number of segment records n segment record
Field information
CHARACT – CHAR 30 Characteristic name
VALUE_CHAR – CHAR 30 Characteristic value

Overview of characteristics used in segment E1BP3060_VALUATION_CHAR

Characteristic name Description Format Comment
Actual potency
ASSAY_FOR_USE Actual potency CHAR 6 (optional, only mandatory if
material is active ingredient)
Optional, only mandatory if
material is active ingredient
Unit of measure in ISO (error comes up, if not
ASSAY_UOM CHAR 3
code for actual potency identical with standard
potency unit within material
master)

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_BatchDat Batch Master Message
a The message will create or update the batch status and batch data based on the
(S) received data.
Since more stocks of material are administered in SAP than known in MES, it may
happen that there are no inventory quantities in MES for the batch data transferred.
Still, this data is loaded into MES.

5.3.2 Message Sample Id Announcement

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered LIMS
IF_SAP_SampleId One sample id per sample step is generated
automatically --- --- 1 
Announcement and sent per process order.
within posting MES

General conditions
 The process order is known in PAS-X prior to sample id announcement.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 41 of 61
Overview of message variants and segments used
Message type
Message variant: ---
ZSAMPLE
Segment
ZE1SAMPLE 
Overview from telegram point of view
Telegram information
Basic type: ZSAMPLE Data information
Extension: ---
Sending system only telegrams with data relating to the site
Filter telegram only telegrams with data relating to MES
Receiving system
(based on a user defined filter)
1 telegram
Number of telegrams in business process
(n message per process order, one per sample step)
Segment information
Structure: ZE1SAMPLE
Definition: ZE1SAMPLE
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
SAMPLE_ID – NUM 10 Sample Id
MATNR – CHAR 18 Produced material
WERKS – CHAR 4 Plant id
AUFNR – CHAR 12 SAP process order number
CHARG – CHAR 10 produced batch
ZVALUE – CHAR 40 Sample step name

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_SampleI Sample Id Announcement
dAnnouncement The message will create sample ids for the given sample step and process order
(N) which will be used for IPC sampling and sample label printing.

5.3.3 Message IPC Result

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered LIMS
IF_SAP_IPCResult automatically --- --- n 
within posting MES

General conditions
 A notification about sampling operations will be issued if the operations are based on sample
ids from LIMS.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 42 of 61
  The results will be posted after the group leader approval.

Overview of message variants and segments used

Message type
Message variant: ---
ZIPC_RESULT
Segment
Z1SAMPLE 
Overview from telegram point of view
Telegram information
Basic type: ZCONFOP Data information
Extension: ---
Sending system only telegrams with relating data to MES
Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per batch)
Segment information
Structure: Z1SAMPLE
Definition: Z2SAMPLE000
Sending system not required
Filter segment
Receiving system not required
n segment record
Number of segment records
(1 per result)
Field information
SAMPLE_ID – NUM 10 Initiating sample id from LIMS
MATERIAL – CHAR 18 Produced material
CHARG – CHAR 10 Produced batch
WERKS – CHAR 4 Constant value
AUFNR – CHAR 12 SAP process order number
MANSTEPNAME – CHAR 40 Manufacturing step name
(step name of sample )
METHODCODE – CHAR 40 Method code
COMPONENTCODE – CHAR 40 Component code
(name of the result)
REPLICATENR – CHAR 40 Replicate number
RESULT – CHAR 40 Result of sample step
UM – CHAR 20 Unit of measure of the result

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_IPCResul Message IPC Result
t The message will post the IPC sample results to LIMS based on a sample id from
(N) LIMS after the group leader approval in MES.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 43 of 61
5.4 Detailed Scheduling

5.4.1 Message Process Order

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered
automatically
when releasing SAP
IF_SAP_POtoMES the order in Y Y 1 
SAP / changes MES
are made after
release

General conditions
 The SAP production scheduler will be mapped to the MES production area.
 The process order data are checked against the MBR data determined by the production
version.
 Alternative BOM items have no component quantity (0.000).
 Updates and deletions are only possible as long as the order is not started yet in MES.

Overview of message variants and segments used

Message type Message variant
ZLOIPRO ---
Segment
E1AFKOL 
Segment
E1JSTKL 
Segment
ZE1AFKOL 
Segment
optional
E1AFFLL
Segment
E1AFVOL 
Segment
E1RESBL 
Segment
E1AFPOL 

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 44 of 61
Overview from telegram point of view
Telegram information
Data information
Basic type: ZLOIPRO01
Extension: ---
Create/Update Delete

Sending system only process orders related to MES

Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per process order)
Segment information
Structure: E1AFKOL
Definition: E2AFKOL001
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
WERKS – CHAR 4 Plant
(constant value)
AUFNR – CHAR 12 SAP process order number
FEVOR – CHAR 3 Production scheduler
MATNR – CHAR 18 Number of the material to be produced
GAMNG – NUM 9,3 Quantity to be produced
GMEIN – CHAR 3 Basic unit of measure in ISO code
GLTRS – DATE Scheduled end date
GLUZS – TIME Scheduled end time
GSTRS – DATE Scheduled start date
GSUZS – TIME Scheduled start time
Segment information
Structure: E1JSTKL
Definition: E2JSTKL
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
STAT – CHAR 5 According to process order status transition matrix
Segment information
Structure: ZE1AFKOL
Definition: ZE1AFKOL000
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
VARNT – CHAR 40 ---
CHARG – CHAR 10 Number of the batch to be produced
RSNUM – NUMC 10 Number of Reservation
(optional)

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 45 of 61
 Telegram information
Data information
Basic type: ZLOIPRO01
Extension: ---
Create/Update Delete

Segment information only for structuring purposes

Structure: E1AFFLL (optional)
Definition: E2AFFLL
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
--- ---
Segment information
Structure: E1AFVOL
Definition: E2AFVOL002
Sending system not required
Filter segment
Receiving system not required
n segment records
Number of segment records
(1 per operation/phase)
Field information
VORNR – CHAR 4 Operation/phase number
PVZNR – CHAR 4 Superior operation number
(optional if phase indicator is not set)
ARBID – CHAR 8 Resource
LTXA1 – CHAR 40 Operation short text
(optional)
SSAVD – DATE Latest scheduled start date
SSAVZ – TIME Latest scheduled start time
SSEDD – DATE Latest cheduled end date
SSEDZ – TIME Latest scheduled end time
Segment information
Structure: E1RESBL
Definition: E2RESBL003
Sending system not required
Filter segment
Receiving system not required
n segment records
Number of segment records
(m per batch and BOM item)
Field information
POSNR – NUMC 4 Position number of BOM
MATNR – CHAR 18 Material number of component
CHARG – CHAR 10 Batch number input material
(optional)
BDMNG – NUM 9,3 Requirement quantity
MEINS – CHAR 3 Basic unit of measure in ISO code
Segment information
Structure: E1AFPOL
Definition: E2AFPOL000
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
VERID – CHAR 4 Recipe version number

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 46 of 61
Process order status transition matrix
SAPStatus MESStatus TargetMESStatus
I0002 (released) NULL 11009 (RMC)
I0013 (delete) NULL -1 (ignore)
I0045 (techn. complete) NULL -1 (ignore)
I0002 (released) 11007 (planned), 11009 (RMC)*
11008 (RFP),
11009 (RMC)
I0013 (delete) 11007 (planned), 11012 (delete)
11008 (RFP), 11009 (RMC)
I0045 (techn. complete) 11007 (planned), 11012 (deleted)
11008 (RFP), 11009 (RMC)
I0002 (released) 11010 (started) -2 (reject)
I0013 (delete) 11010 (started) -2 (reject)
I0045 (techn. complete) 11010 (started) -2 (reject)
I0002 (released) 11011 (finished), 11012 (deleted), -1 (ignore)
11013 (aborted)
I0013 (delete) 11011 (finished), -2 (reject)
11013 (aborted)
I0013 (delete) 11012 (deleted), -1 (ignore)
I0045 (techn. complete) 11011 (finished), 11012 (deleted), -1 (ignore)
11013 (aborted)
* Manufacturing order is deleted and recreated with target MES status

Interface Message Brief Description

ID Description
(Change Flag)
IF_SAP_POtoMES Process Order Message
(C) Process orders created in SAP are automatically reported to MES when they reach
the status "Released".
Based on the received data and the specified MBR MES will create and release a
manufacturing order accordingly.
The batch reservation might be part of this message.
The status transitions are done according to the status transition matrix.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 47 of 61
5.5 Production Execution

5.5.1 Status Data

[Link] Message Start Manufacturing Order

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered MES
IF_SAP_StartMO automatically --- --- 1 
within posting SAP

General conditions
---

Processing triggered in receiving system SAP

The actual start date of the concerning process order will be set.
The process order will be blocked against further changes.
Transfer orders in order to fulfill the concerning material staging operation are started.

Overview of message variants and segments used

Message type
Message variant: STA
LOIPRO
Segment
E1AFKOL 
Segment
E1JSTKL 
Overview from telegram point of view
Telegram information
Basic type: LOIPRO01
Data information
Extension: ---

Sending system not required

Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per manufacturing order)
Segment information
Structure: E1AFKOL
Definition: E2AFKOL001
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
WERKS – CHAR 4 Plant
(constant value)

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 48 of 61
 Telegram information
Basic type: LOIPRO01
Data information
Extension: ---

AUFNR – CHAR 12 SAP process order number

MATNR – CHAR 18 Number of material to be produced
GAMNG – NUM 9,3 Quantity to be produced
BMEINS – CHAR 3 Basic unit of measure in ISO code
GSTRP – DATE Earliest start date
GLTRP – DATE Latest end date
AUTYP – CHAR 2 „01“
Segment information
Structure: E1JSTKL ---
Definition: E2JSTKL
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
STAT – CHAR 5 „E0016“ (Start)

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_StartMO Start message for manufacturing order
(S) The start information is automatically reported to SAP when the manufacturing
order changes into the defined MES status “Start”.

[Link] Message Performance Data of Shop Floor Order

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered
For cost accounting purposes, the
automatically MES
IF_SAP_Performanc production times of both resource and
within posting --- --- 1 
eData personnel of each shop floor order are
(end of shop SAP
acquired in PAS-X and reported to SAP.
floor order)

Overview of message variants and segments used

Message type
Message variant: ---
ZCONFOP
Segment
ZCONFOP 

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 49 of 61
Overview from telegram point of view:
Telegram
Basic type: ZCONFOP Data information
Extension: ---
Sending system only telegrams with relating data to MES
Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per shop floor order)
Segment information
Structure: Z1CONFOP
Definition: Z1CONFOP000
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
AUFNR – CHAR 12 SAP process order number
VORNR – CHAR 4 SAP operation number
ISM01 – NUM 13,3 setup and cleaning time of personnel in hours
ISM02 – NUM 13,3 setup and cleaning time of resource in hours
ISM03 – NUM 13,3 production time of personnel in hours
ISM04 – NUM 13,3 production-time of resource in hours

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_Performa Performance Data of Shop Floor Order
nceData (N) After each shift all times are acquired by the operator and accumulated per
shop floor order, the times are entered in a basic function with activities of
type measured value. On completion of a shop floor order and after the
production times of resource and personnel are acquired and confirmed the
message creation is triggered.

[Link] Message Abort Manufacturing Order

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered MES
IF_SAP_MOAbort automatically --- --- 1 
within posting SAP

General conditions
---

Overview of message variants and segments used

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 50 of 61
 Message type
Message variant: STA
LOIPRO
Segment
E1AFKOL 
Segment
E1JSTKL 
Overview from telegram point of view
Telegram information
Basic type: LOIPRO01
Data information
Extension: ---

Sending system not required

Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per manufacturing order)
Segment information
Structure: E1AFKOL
Definition: E2AFKOL001
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
WERKS – CHAR 4 Plant
(constant value)
AUFNR – CHAR 12 SAP process order number
MATNR – CHAR 18 Number of material to be produced
GAMNG – NUM 9,3 Quantity to be produced
BMEINS – CHAR 3 Basic unit of measure in ISO code
GSTRP – DATE Earliest start date
GLTRP – DATE Latest end date
AUTYP – CHAR 2 „01“
Segment information
Structure: E1JSTKL ---
Definition: E2JSTKL
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
STAT – CHAR 5 „E0017“ (abort)

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_ Abort Message for Manufacturing Order
MOAbort The abort message is automatically reported to SAP when the manufacturing order
(S) changes into the status “Finished” and if shop floor orders are in the status
“Aborted”.
The abort message replaces the normal completed/finishing message for a
manufacturing order.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 51 of 61
[Link] Message End Manufacturing Order
Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered MES
IF_SAP_MOEnd automatically --- --- 1 
within posting SAP

General conditions
---

Overview of message variants and segments used

Message type
Message variant: STA
LOIPRO
Segment
E1AFKOL 
Segment
E1JSTKL 
Overview from telegram point of view
Telegram information
Basic type: LOIPRO01 Data information
Extension: ---
Sending system not required
Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per manufacturing order)
Segment information
Structure: E1AFKOL
Definition: E2AFKOL001
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
WERKS – CHAR 4 Plant
(constant value)
AUFNR – CHAR 12 SAP process order number
MATNR – CHAR 18 Number of material to be produced
GAMNG – NUM 9,3 Quantity to be produced
BMEINS – CHAR 3 Basic unit of measure in ISO code
GSTRP – DATE Earliest start date
GLTRP – DATE Latest end date
AUTYP – CHAR 2 „01“

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 52 of 61
 Telegram information
Basic type: LOIPRO01 Data information
Extension: ---
Segment information
Structure: E1JSTKL ---
Definition: E2JSTKL
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
STAT – CHAR 5 „I0045“ (TECO)

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_MOEnd Finishing Message for Manufacturing Order
(S) The finishing message is automatically reported to SAP when the manufacturing
order changes into the MES status “Finished” and if no shop floor order is in the
status “Aborted”.

[Link] Message Group Leader Approval for Manufacturing Order

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered MES
IF_SAP_ApproveGLA automatically --- --- 1 
within posting SAP

General conditions
 The group leader approval must be activated in PAS-X explicitly via a configuration
variable in order to be sent.

Overview of message variants and segments used

Message type
Message variant: STA
LOIPRO
Segment
E1AFKOL 
Segment
E1JSTKL 

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 53 of 61
Overview from telegram point of view
Telegram information
Basic type: LOIPRO01
Data information
Extension: ---

Sending system not required

Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per manufacturing order)
Segment information
Structure: E1AFKOL
Definition: E2AFKOL001
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
WERKS – CHAR 4 Plant
(constant value)
AUFNR – CHAR 12 SAP process order number
MATNR – CHAR 18 Number of material to be produced
GAMNG – NUM 9,3 Quantity to be produced
BMEINS – CHAR 3 Basic unit of measure in ISO code
GSTRP – DATE Earliest start date
GLTRP – DATE Latest end date
AUTYP – CHAR 2 „01“
Segment information
Structure: E1JSTKL ---
Definition: E2JSTKL
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
STAT „E0009“ (GLA)

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_ Group Leader Approval Message for Manufacturing Order
ApproveGLA Finishing the group leader approval will trigger the message creation.
(N)

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 54 of 61
[Link] Message Production Pharmacist Approval for Manufacturing Order
Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered MES
IF_SAP_ApprovePPA automatically --- --- 1 
within posting SAP

General conditions
---

Triggering event in sending system PAS-X

Finishing the production pharmacist approval will trigger the message creation.

Processing triggered in receiving system SAP

The status of the concerning process order will be set to ‘production pharmacist approval’ (PPA).

Overview of message variants and segments used

Message type
Message variant: STA
LOIPRO
Segment
E1AFKOL 
Segment
E1JSTKL 
Overview from telegram point of view
Telegram information
Basic type: LOIPRO01
Data information
Extension: --

Sending system not required

Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per manufacturing order)
Segment information
Structure: E1AFKOL
Definition: E2AFKOL001
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
WERKS – CHAR 4 Plant
(constant value)
AUFNR – CHAR 12 SAP process order number
MATNR – CHAR 18 Number of material to be produced
GAMNG – NUM 9,3 Quantity to be produced
BMEINS – CHAR 3 Basic unit of measure in ISO code
GSTRP – DATE Earliest start date

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 55 of 61
 Telegram information
Basic type: LOIPRO01
Data information
Extension: --

GLTRP – DATE Latest end date

AUTYP – CHAR 2 „01“
Segment information
Structure: E1JSTKL ---
Definition: E2JSTKL
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
STAT „E0007“ (PPA)

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_ Production Pharmacist Approval Message for Manufacturing Order
ApprovePPA The status of the concerning process order will be set to ‘production pharmacist
(N) approval’ (PPA).

[Link] Message Quality Assurance Approval for Manufacturing Order

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered MES
IF_SAP_ApproveQA
automatically --- --- 1 
A
within posting LIMS

General conditions
---

Overview of message variants and segments used

Message type
Message variant: ---
ZLOIPRO02
Segment
ZAFKOL 
Segment
ZE1JSTKL 
Overview from telegram point of view

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 56 of 61
 Telegram information
Basic type: ZLOIPRO02
Data information
Extension: ---

Sending system not required

Filter telegram
Receiving system not required
1 telegram
Number of telegrams in business process
(per manufacturing order)
Segment information
Structure: ZAFKOL
Definition: ZAFKOL000
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
AUFNR – CHAR 12 SAP process order number
MATNR – CHAR 18 Number of material to be produced
CHARG – CHAR 10 Produced batch
Segment information
Structure: ZE1JSTKL ---
Definition: ZE2JSTKL
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record
Field information
APPRNAME – CHAR 80 Approver of the Batch Record
(user id of PAS-X user)
APPRDATE – DATE Batch Record approval date
APPRTIME – TIME Batch Record approval time

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_ Quality Assurance Approval Message for Manufacturing Order
ApproveQAA The status of the concerning process order will be set to ‘quality assurance
(N) approval’ (QAA).

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 57 of 61
5.5.2 Stock Data

[Link] Message Take Out on Manufacturing Order

Interface Trigger Telegram Remark
Message ID
Creation Updat Cancel Num Direc
e ber tion
triggered MES
IF_SAP_
automatically --- Y n 
OrderWithdrawal
within posting SAP

General conditions
 A load does not contain different material or batch quantities.
 Each consumption of a load will be transferred in a separate message.
 The reservation item number will be determined in SAP.
 In case that the inventory in SAP is not sufficient to carry out the announced consumption
posting the SAP inventory will be adjusted internally prior to performing the consumption.
 Consumption messages of materials that are flagged as ‘not relevant for consumption’ will not
be sent.

Overview of message variants and segments used

Message type
Message variant: ---
WMMBXY
Segment
E1MBXYH 
Segment
E1MBXYI 
Overview from telegram point of view
Telegram information
Data information
Basic type: WMMBID02
Extension: ---
Posting Cancel
Sending system only for material registered as inventory
Filter telegram
Receiving system not required
n telegrams per manufacturing order but
Number of telegrams in business process
1 telegram per consumption operation
Segment information
Structure: E1MBXYH
Definition: E2MBXYH001
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record as header data
Field information
BLDAT – DATE current date
BUDAT – DATE current date
TCODE – CHAR 4 „MB1A” MIGO

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 58 of 61
 Telegram information
Data information
Basic type: WMMBID02
Extension: ---
Posting Cancel
Segment information
Structure: E1MBXYI
Definition: E2MBXYI002
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record as item data
Field information
BWART – CHAR 3 „261“ „262“
WERKS – CHAR 4 Plant
(constant value)
MATNR – CHAR 18 Material number
LGORT – CHAR4 SAP storage location
LGTYP - CHAR 3 SAP storage type
(optional, only if specified in MES)
LGPLA - CHAR 10 SAP storage bin
(optional, only if specified in MES)
CHARG – CHAR 10 Batch number
(optional, mandatory if material is handled in batches)
INSMK – CHAR 1 ---
ERFMG – NUM 10,3 Consumed quantity
ERFME – CHAR 3 Basic unit of measure in ISO code
KZBEW – CHAR 1 ---
SGTXT – CHAR 50 Pallet id
AUFNR – CHAR 12 SAP process order number
KOSTL – CHAR 10 ---
UMLGO – CHAR 4 ---

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_OrderWit Consumption message for manufacturing order
hdrawal The information on consumption for a manufacturing is automatically reported to
(S) SAP upon the posting.

[Link] Message Stock Creation on Manufacturing Order

Interface Message Trigger Telegram Remark

ID
Creation Updat Cancel Num Direc
e ber tion
triggered MES
IF_SAP_OrderReceipt automatically --- Y n 
within posting SAP

General conditions
 A load does not contain different material or batch quantities.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 59 of 61
  Every addition is transferred in a separate message.
 The pallet id is generated in PAS-X (material no. + batch no. + sequence no. (unique per
material/batch combination))
 The cancellations of stock creation must be activated in the distribution model of PAS-X
interface layer explicitly in order to be sent.

Overview of message variants and segments used

Message type
Message variant: ---
WMMBXY
Segment
E1MBXYH 
Segment
E1MBXYI 
Overview from telegram point of view
Telegram information
Data information
Basic type: WMMBID02
Extension: ---
Posting Cancel
Sending system only for material registered as inventory
Filter telegram
Receiving system not required
n telegrams per manufacturing order but
Number of telegrams in business process
1 telegram per goods receipt operation
Segment information
Structure: E1MBXYH
Definition: E2MBXYH002
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record as header data
Field information
BLDAT – DATE current date
BUDAT – DATE current date
TCODE – CHAR 4 „MB31”
Segment information
Structure: E1MBXYI
Definition: E2MBXYI002
Sending system not required
Filter segment
Receiving system not required
Number of segment records 1 segment record as item data
Field information
BWART – CHAR 3 „101“ „102“
WERKS – CHAR 4 Plant
(constant value)
MATNR – CHAR 18 Material number
LGORT – CHAR4 SAP storage location
LGTYP - CHAR 3 SAP storage type
(optional, only if specified in MES)
LGPLA - CHAR 10 SAP storage bin
(optional, only if specified in MES)
CHARG – CHAR 10 Batch number
INSMK – CHAR 1 „X“

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 60 of 61
 Telegram information
Data information
Basic type: WMMBID02
Extension: ---
Posting Cancel
ERFMG – NUM 10,3 Produced quantity
ERFME – CHAR 3 Basic unit of measure in ISO code
KZBEW – CHAR 1 „F“
SGTXT – CHAR 50 Pallet id
AUFNR – CHAR 12 SAP process order number
KOSTL – CHAR 10 ---
UMLGO – CHAR 4 ---

Interface Brief Description

Message ID Description
(Change Flag)
IF_SAP_ Goods receipt message for manufacturing order
OrderReceipt The goods receipt information for the manufacturing order is automatically reported
(S) to SAP upon the posting.

Version: V0.1 - Date of this version: 24-06- 2022

Document name: PAS-X-SAP Interface
Page 61 of 61