Mapping fields between SAP Ariba and ECC for integration can vary depending on the specific integration scenario and the version of each system being used. However, some commonly mapped fields include:
Master Data
- Vendor/Supplier:
- Ariba Supplier ID <-> ECC Vendor Number
- Supplier Name
- Address Information
- Contact Information
- Bank Details
- Material/Product:
- Ariba Product ID <-> ECC Material Number
- Product Description
- Unit of Measure
- Pricing Information
Transactional Data
- Purchase Orders:
- Ariba PO Number <-> ECC PO Number
- PO Date
- PO Line Items (Material, Quantity, Price, etc.)
- Ship-to Address
- Bill-to Address
- Invoices:
- Ariba Invoice Number <-> ECC Invoice Number
- Invoice Date
- Invoice Amount
- PO Reference
- Invoice Line Items
- Goods Receipts:
- Ariba GR Number <-> ECC GR Number
- GR Date
- PO Reference
- GR Line Items (Material, Quantity, etc.)
Additional Considerations
- Custom Fields: It's common to have custom fields in both Ariba and ECC that need to be mapped for specific business requirements.
- Mapping Direction: Data mapping can be bi-directional or unidirectional depending on the integration scenario.
- Data Transformation: Sometimes data transformation or conversion is required to ensure compatibility between the systems.
Important Note:
- The above list is not exhaustive and can vary based on your specific implementation.
- It is critical to engage with experienced SAP Ariba and ECC consultants to understand the precise mapping requirements for your integration project.
- SAP provides documentation and tools (like the CIG - Cloud Integration Gateway) to assist with mapping and integration.
Please let me know if you would like to explore specific integration scenarios in more detail.
No comments:
Post a Comment