This simulation demonstrates how to use a cloud integration component to import BOM from SAP.
Working with Bill of Materials (BOMs)
Objective
After completing this lesson, you will be able to explain how to work with Bills of Materials (BOMs).
Using SAP Ariba AddOn to Import BOM from SAP
Monitor and Manage BOM Uploads from Cloud Integration Gateway
SAP Ariba Strategic Sourcing Suite uses the SAP Ariba Cloud Integration Gateway to automatically receive BOM data from SAP ERP.
This simulation demonstrates how to monitor and manage BOM uploads from Cloud Integration Gateway.
A BOMReplicateRequest message with BOM data from SAP ERP is sent to Cloud Integration Gateway. Cloud Integration Gateway transforms the data into a payload for each BOM and sends it to product sourcing as a SOAP request.
The BOMs are processed and validated asynchronously as they are received. If a BOM fails, the other BOMs continue to be processed.
Example: A BOM has a top BOM, assembly 1, and assembly 2. A total of three payloads are sent to SAP Ariba, one for each BOM structure.
Note
The scheduled task, BOM Upload Service Processor for CIG, located in the Product Sourcing Manager → Scheduled Tasks page uploads the BOMs asynchronously as a service.Monitor BOM Upload Confirmations Sent to Cloud Integration Gateway
A BOM confirmation message is created when product sourcing has finished processing the BOM replication request from the SAP Ariba Cloud Integration Gateway.
The confirmation message is sent back to SAP ERP through Cloud Integration Gateway. The message informs SAP ERP that the BOM upload was received and whether the load was a success or failure.
Status messages about the success or failure of the load are sent back to SAP ERP in a SOAP request (BOMConfirmation) through Cloud Integration Gateway. The status message includes a universally unique ID (UUID) created by Cloud Integration Gateway when the BOMs are sent.
The ID lets you know the material, BOM number, BOM category, response code, and whether the load was a success or failure. If the load failed, the status message information is used to correct the error and resend the load from SAP ERP.
This simulation demonstrates how to monitor BOM upload confirmations sent to Cloud Integration Gateway.
Change Master Integration
The change master record is a master record that contains information necessary for the management and controls changes for a material or BOM.
The change master record contains data of:
- Descriptive character such as the reason for the change.
- Control data such as effectivity data & object type indicators.
Besides this the change master also holds user maintained data as well as the data that is automatically updated by the system, e.g. management data.
Process flow
- Create a new change master number.
- Assign the change number to a material.
- Create and view the revision history of material using the change master number.
- Export the change master to SAP Ariba Product Sourcing.
- Monitor the exported data in CIG.
- Validate the record in SAP Ariba Product Sourcing.
Change Master Integration: Creation of Change Master
Change Master Integration: Assign the Change Number to a Material
Change Master Integration: Create and View the Revision History of Material
Change Master Integration: Export Change Master to SAP Ariba Product Sourcing
Using Ariba AddOn program ARBCIG_CHANGE_MASTER_EXPORT, the change master data can be extracted from SAP system to Ariba Product Sourcing.
We have different modes of extraction:
- Full Mode: Extracts all the change numbers available in the system.
- Incremental Mode: Extracts the change numbers which is created or updated after the last run.
- Custom Mode: If we want to extract specific change numbers created on a specific date and time.
- Packet Size: Change numbers extraction will split according to the packet size. For example: If the number of change numbers in the system are 100 and the packet size is 10 then the system extracts the change number in different payloads where each payload holds 10 change numbers.
Change Master Integration: Monitor the Exported Data in CIG
In Transaction Tracker, filter with document type Change Master Request.
Change Master Integration: Validate the Record in SAP Ariba Product Sourcing
Go to the Advanced Search in the Product Sourcing dashboard and use the Change Number filter.
Product Data eXchange (PDX) Web Service
You can use the PDX web service to upload BOM documents in PDX format from an external system or file.
In sites integrated with SAP ERP, you can preload master data and use PDX to load BOMs.
PDX web service uses standard field mapping. You can also map item material master data received from SAP ERP to custom (new) product sourcing fields for items in BOMs and material lists.
The BOM upload PDX web service conforms to the Representational State Transfer (REST) architecture model. The BOM upload PDX web service accepts HTTP POST requests that contain BOM data in PDX format. The PDX data must conform to the IPC-2578 standard, which is part of the IPC 2570 series of specifications published by the Association Connecting Electronics Industries.
Limitations
If you have multiple PDX files, they must have the same structure. If you have multiple BOMs in one PDX file, they must have the same structure.
The maximum PDX file size is 100 MB.
BOM Upload PDX Web Service Request
Send BOM PDX data in an HTTP POST request to a URL in the following format: https://mySAPAribaSourcingDomain/dms/bom/importPDX?realm=myAribaSiteName&erpId=mySAPERPId&fileName=fileName
Where:
- mySAPAribaSourcingDomain is the domain you see in your browser's address window when you are logged in to SAP Ariba Sourcing or SAP Ariba Strategic Sourcing Suite, such as myCompany.sourcing.ariba.com.
- mySAPAribaSiteNameis your site name for the SAP Ariba Sourcing solution. If you do not know your site name, you can get it from your SAP Ariba representative.
- mySAPERPId is the PDX default SAP ERP external system assigned to your realm.
- fileName is the name of the file you are sending. The file name must be .pdx and the file must contain a pdx.xml file inside it.
BOM PDX Document Elements
The BOM PDX document contains an Item element with one or more item elements. SAP Ariba Strategic Sourcing Suite accepts all child elements of an Item element, but uses data from only the following elements:
- AdditionalAttributes
- BillOfMaterial
- ApprovedManufacturerList
SAP Ariba Strategic Sourcing Suite ignores data sent in all other child elements of Item elements (History, Attachments, ChangeHistory, Characteristics, AlternateItems, SerialNumbers, and AlternateIdentifiers).
An Item element can describe a BOM or material. If an item describes a BOM, the identities of the child materials or BOMs are specified as follows:
<BillOfMaterial>
<BillOfMaterialItem billOfMaterialItemIdentifier="child_itemIdentifer" ...>
Where: child_itemIdentifier corresponds to the itemIdentifier attribute value of the item that describes the child.
An Item element can also contain an ApprovedManufacturerList element that contains AML entries for the item. The ApprovedManufacturerList contains one or more ApprovedManufacturerListItem elements; each of these elements contain manufacturer information for the item.
Item Attributes
SAP Ariba Strategic Sourcing Suite uses the following attribute values specified for an Item element:
| Item Attribute | Description |
|---|---|
| description | Stored by SAP Ariba and displayed in the SAP Ariba Name field for the item. |
| itemIdentifier | Stored by SAP Ariba and displayed in the SAP Ariba Item ID field for the item. |
| globalProductUnitOfMeasureCode | Stored by SAP Ariba and displayed in the SAP Ariba Unit of Measure field for the item. |
| itemClassification | Stored by SAP Ariba but not displayed. |
| makeBuy | Stored by SAP Ariba but not displayed. |
| ﹤AdditionalAttributes groupLabel="OnePDM"﹥ (child element) | |
| ﹤AdditionalAttribute name="PartTypeId" value="nnn" /﹥ (child element) | Stored by SAP Ariba and displayed in the SAP Ariba Part Type ID field. This value is also mapped to the Part Type for the item if the Part Type ID is already in your product sourcing solution. |
In addition, SAP Ariba sets the Valid From field for the item to the date it receives the PDX.
Bill of Materials Item Attributes
SAP Ariba Strategic Sourcing Suite uses the following attribute values specified for a BillOfMaterialItem element:
| BillOfMaterial Attribute | Description |
|---|---|
| billOfMaterialItemIdentifier | Stored by SAP Ariba and displayed in the SAP Ariba Item ID field (refers to the Item with the same value in the itemIdentifier attribute). |
| itemQuantity | Stored by SAP Ariba and displayed in the SAP Ariba Quantity field. |
Approved Manufacturer List Item Attributes and Child Elements
SAP Ariba Strategic Sourcing Suite uses the following attribute values and child elements for an ApprovedManufacturerListItem element:
| ApprovedManufacturerListItem Attribute or Child Element | Description |
|---|---|
| manufacturerPartIdentifier (attribute) | Stored by SAP Ariba and displayed in the SAP Ariba Supplier Item ID field. |
| ﹤AdditionalAttribute name="SAPVendorId" value="nnn" /﹥ (child element) | Stored by SAP Ariba and displayed in the SAP Ariba SAP Vendor ID field. This value is also mapped to a SAP Ariba Strategic Sourcing solutions supplier ID, which is displayed in the SAP Ariba Supplier ID field. |
| ﹤AdditionalAttribute name="Vendor Legal Name" value="nnn" /﹥ (child element) | Stored by SAP Ariba and displayed in the SAP Ariba Supplier Name field. |
BOM PDX Example
BOM Upload Using CSV Files
If design BOMs are not released to ERP systems, SAP Ariba allows you to import them in CSV format. Once imported, you can perform sourcing activities, such as establish suppliers, estimate costs, and define high-level contracts with suppliers.
Prerequisites
- The site must be configured for product sourcing and be enabled for BOM sourcing.
- To upload BOMs, users must have Administrator access.
BOM in CSV Format
The BOM in CSV format allows you to define what data is included in the BOM, such as BOM level, BOM number, material number, validity, BOM text, item category, and quantity.
Users can track the status of the uploaded BOMs, validation errors, failure messages, and success messages. In the case of validation errors, users can carry out corrections.
The product sourcing functionality creates the BOM along with the materials. The BOM can be viewed and used just like any other BOM for the purpose of assignment, sourcing, and cost roll-up calculation.
Log in to track your progress & complete quizzes