Materials Consumed Guidelines (OB IDoc)
See How To Use this Guide before interpreting the guidelines below.
Message Type: MATERIALS_CONSUMED
Info Exchange Display Name: Materials Consumed
Data Element | Occurs | Format | Length | Enums | Req | Description | |||
---|---|---|---|---|---|---|---|---|---|
MBGMCR02 | 1…1 | - | - | - | M | XML IDoc MBGMCR root element. Please note: this guideline lists segments and fields that may be populated in materials consumed basic type MBGMCR02 for postings and reversals. Most data elements listed will not be populated in any given instance of the IDoc. | |||
IDOC | 1…1 | - | - | - | M | IDoc root. | |||
@BEGIN | 1…1 | String | 0/* | - | M | Begin of message attribute.1 | |||
EDI_DC40 | 1…1 | - | - | - | M | IDoc control record. | |||
@SEGMENT | 1…1 | String | 0/* | - | M | Begin of segment attribute.2 | |||
TABNAM | 1…1 | String | 0/* | - | M | IDoc table name. Mandatory. Identifies control segment.3 | |||
MANDT | 0…1 | String | 0/3 | - | M | Client number of sending or receiving SAP system.4 | |||
DOCNUM | 0…1 | String | 0/16 | - | M | IDoc number of sending SAP system. Will not post to customer system, which will generate its own IDoc number. This is a mandatory value for IDocs sent to TraceLink. SAP will always send the IDoc number.5 | |||
DOCREL | 0…1 | String | 0/4 | - | O | IDoc version release number.6 | |||
STATUS | 0…1 | String | 0/2 | - | O | Current processing status of IDoc in sending system. Not relevant for receiving system.7 | |||
DIRECT | 0…1 | String | 0/* | - | O | Direction is in relation to sending or receiving SAP system. 1 = outbound from sender, 2 = inbound to receiver.8 | |||
TEST | 0…1 | String | 0/1 | - | M | Test message indicator. If Test flag in partner profile is set, this field will contain X, otherwise it will be null. This is a mandatory field for TraceLink BUT A NULL VALUE IS VALID. Valid entries are: X = Test flag is set (Test message). Null or empty = Default. Test flag is not set: Production message. Note if the test flag is set in the IDoc, it must also be set in the partner profile in the sender or receiver's SAP system. | |||
IDOCTYP | 1…1 | String | 0/30 | - | M | IDoc basic type. Identifies the IDoc structure that stores the data from the SAP document or message.9 | |||
MESTYP | 1…1 | String | 0/* | - | M | IDoc logical message type identifies the SAP business object.10 | |||
SNDPOR | 1…1 | String | 1/10 | - | M | Sender port (SAP System, EDI subsystem) The sender port is different for the sender or receiver of an IDoc. For the IDoc sender this is the logical port in his SAP system, a concatenation of <SAP><SysID>. Your system will automatically generate this value. For the IDoc receiver, this is the XML file or other port set up in WE21 that defines the port used to send OB IDocs to the sender. This is a mandatory value can be entered into TraceLink IDoc configuration by the IDoc receiver.11 | |||
SNDPRT | 1…1 | String | 1/2 | - | M | Partner type of sender. Outbound from SAP this will be always set by the system to LS for logical system. Inbound to SAP this value must match the partner type set for the sender in the inbound partner profile. This can be set in TraceLink IDoc configuration by the IDoc receiver.12 | |||
SNDPFC | 0…1 | String | 0/2 | - | O | Partner function of sender. Set in the partner profile. Mandatory if defined in the partner profile. Partner function is linked to partner type; e.g. partner type KU can have partner function SP (sold-to), BP (bill-to), SH (ship-to) and so on. Partner type LI (Vendor) can have partner function VN (Vendor), DP (Delivering Plant), HR (Manufacturer), and so on. Outbound from SAP this value is null. Inbound to SAP it must match the partner function in the inbound partner profile if it has been set. It can be entered into TraceLink configuration by the receiver of the IDoc. | |||
SNDPRN | 1…1 | String | 1/10 | - | M | SAP partner number for sender. OB from SAP this is the logical system name for the sending SAP system. Inbound to SAP this is the sender's SAP partner number used in the inbound partner profile. If using TraceLink recommended logical system configuration, this would be TRACELINK IB to SAP.13 | |||
SNDLAD | 1…1 | String | 1/70 | - | M | Logical address of sender. Site ID for sending party. This is the supplier’s site ID for the materials issue message. This is a critical value for TraceLink. Please note: SNDLAD and RCVLAD are combined in TraceLink to form the ProcessLink ID, which identifies the specific ProcessLink at which the current message is targeted. All messages communicated through TraceLink must be defined within a ProcessLink via the ProcessLink ID.14 | |||
RCVPOR | 1…1 | String | 1/10 | - | M | SAP receiver port. The receiver port is different for the sender or receiver of an IDoc. For the IDoc sender, outbound from SAP, this is the XML file or other port set up in WE21 that defines the port used to send IDocs to the receiver. It is taken from the port defined in the outbound partner profile. For the IDoc receiver, inbound to SAP, this is the logical port in his SAP system, a concatenation of <SAP><SystemID>. This is a mandatory value and can be entered into TraceLink configuration by the IDoc receiver.15 | |||
RCVPRT | 1…1 | String | 1/2 | - | M | Partner type of receiver. Inbound to SAP this be set to LS (logical system) by the system. Outbound from SAP it will come from the partner type in outbound partner profile.16 | |||
RCVPFC | 0…1 | String | 0/2 | - | O | Partner function of receiver. Mandatory if in partner profile. Like SNDPFC this is linked to partner type. Outbound from SAP it will be pulled from the outbound partner profile, if present. Inbound to SAP it will not be populated. | |||
RCVPRN | 1…1 | String | 1/10 | - | M | Receiver partner in SAP. Must match OB partner profile in sending system or SAP logical system in receiving system.17 | |||
RCVLAD | 1…1 | String | 1/70 | - | M | Logical address of receiver. Company ID for receiving party. This is the customer for the materials issue message. See SNDLAD for more information.18 | |||
CREDAT | 0…1 | String | 0/8 | - | M | Date IDoc was created in format YYYYMMDD. IDoc date is mandatory for TraceLink.19 | |||
CRETIM | 0…1 | String | 0/6 | - | M | Time IDoc was created in format HHMMSS. IDoc time is mandatory for TraceLink.20 | |||
E1BP2017_GM_HEAD_01 | 0…1 | - | - | - | M | Material document header segment. | |||
@SEGMENT | 1…1 | String | 0/* | - | M | Begin of segment attribute.21 | |||
PSTNG_DATE | 0…1 | String | 0/8 | - | O | Date the material document posts to finance.22 | |||
DOC_DATE | 0…1 | String | 0/8 | - | M | Document date - date the material is consumed by the supplier. This date is mandatory for TraceLink.23 | |||
REF_DOC_NO | 0…1 | String | 0/16 | - | O | Reference Document Number. Reference document number. Can be the external document from which the DOC_DATE is pulled. Goes into the header of the material document.24 | |||
BILL_OF_LADING | 0…1 | String | 0/16 | - | O | Bill of lading number.25 | |||
PR_UNAME | 0…1 | String | 0/12 | - | O | Name of user who created document.26 | |||
HEADER_TXT | 0…1 | String | 0/25 | - | O | Free form text for header of receiver’s material document. Can describe reference document and/or date.27 | |||
E1BP2017_GM_CODE | 0…1 | - | - | - | O | GM code linking to inventory posting message in table T158G. | |||
@SEGMENT | 1…1 | String | 0/* | - | M | Begin of segment attribute.28 | |||
GM_CODE | 0…1 | String | 0/2 | TransactionCodes | O | GM code linked to SAP material movement message in table T158G. Messages linked to specific movement types but perform generally same function as message MIGO: post a material movement into inventory management. This value is optional inbound to TraceLink, outbound from the supplier. However it is a mandatory value for posting to a receiving SAP system.29 | |||
E1BP2017_GM_ITEM_CREATE | 0…* | - | - | - | M | Create goods movement (material document) item. IDoc segment provides item level data to create the goods movement message. This is the most important segment in the IDoc, both for inbound and outbound usage, and must be present to post the goods movement in the receiving system. It is extracted from (outbound from SAP), or posted to (inbound to SAP), table MSEG. Please note that the entire structure of the segment is presented but only a small sub-set of fields are actually populated. | |||
@SEGMENT | 1…1 | String | 0/* | - | M | Begin of segment attribute.30 | |||
MATERIAL | 0…1 | String | 0/18 | - | M | Material Number. Customer material number of item posting goods movement. Note: For outbound from SAP IDocs, TraceLink (TL) will strip leading zeroes from purely numeric customer material numbers during its inbound translation. For inbound to SAP IDoc interfaces, TL pads the customer material number to 18 characters with leading zeroes, if it is a purely numeric ID.31 | |||
PLANT | 0…1 | String | 0/4 | - | O | Plant location identifier that product posted against.32 | |||
STGE_LOC | 0…1 | String | 0/4 | - | O | Storage Location for posting material.33 | |||
BATCH | 0…1 | String | 0/10 | - | M | Customer lot/batch number.34 | |||
MOVE_TYPE | 0…1 | String | 0/3 | - | O | SAP Movement Type (Inventory Management). Drives goods movement type, such as goods receipt or goods issue, for consumed material in SAP. The movement type also determines whether the movement is a posting or a reversal message. This value is being mapped without validation in TraceLink. The system will map whatever it receives.35 | |||
VENDOR | 0…1 | String | 0/10 | - | O | SAP Vendor Account Number.36 | |||
CUSTOMER | 0…1 | String | 0/10 | - | O | SAP customer account number.37 | |||
ENTRY_QNT | 0…1 | String | 0/15 | - | M | Quantity in unit of entry.38 | |||
ENTRY_UOM | 0…1 | String | 1/3 | UnitOfMeasure | M | Unit of Entry.39 | |||
PO_NUMBER | 0…1 | String | 0/10 | - | M | Purchase Order (PO) number. Customer PO number links to TraceLink PO. Required value. Multiple POs can be sent within the same file as long as each included PO is within the same ProcessLink and each PO line Item is associated with one work order.40 | |||
PO_ITEM | 0…1 | String | 0/5 | - | M | PO line item number. Matches item number in customer PO. Each PO line Item must be associated with one work order. Required value.41 | |||
ITEM_TEXT | 0…1 | String | 0/50 | - | O | Material text description. | |||
GR_RCPT | 0…1 | String | 0/12 | - | O | Goods recipient/ship-to party. | |||
ORDERID | 0…1 | String | 0/12 | - | M | Process/work order number. Links to PO for consumption of item. Required for outbound to TraceLink. Only sent from TraceLink to receiving system if goods movement to or from production order. Only one document, PO or Work Order, can be used to post a goods movement to a customer’s target SAP system.42 | |||
MVT_IND | 0…1 | String | 0/1 | - | O | Movement indicator. Describes
reference document type for SAP inventory movement. PO. Valid
values:
![]() |
|||
PROD_DATE | 0…1 | String | 0/8 | - | O | Date of manufacture or production date. Posts to material document field HSDAT during inbound to SAP processing. Outbound, the Date of Production should be the Date of Manufacture of the component material (API, bulk, etc.) and not the date that the finished goods were produced. Note: Used for materials produced, not required for materials consumed. | |||
VENDRBATCH | 0…1 | String | 0/15 | - | O | Supplier's batch identifier. | |||
MATERIAL_EXTERNAL | 0…1 | String | 0/40 | - | O | External material number. TraceLink uses this as the Supplier's material number in the outbound from the supplier’s IDoc. This field is not sent to the customer's system for the material movement during inbound into SAP processing.43 |