Issue

Syensqo has multiple EDI setups using various applications. EDI (Electronic Data Interchange) involves the electronic exchange of standardized business documents between organizations (B2B). This KDD aims to analyze the EDI applications used for each process and provide recommendations for the applications.

The systems that are used and the stream that uses them are

Recommendation

Review consoildation on standard tools - eg Ariba Network.

Background & Context

EDI stands for Electronic Data Interchange. It is a standardized method for exchanging business documents between organizations electronically. EDI enables companies to send and receive documents such as purchase orders, invoices, and shipping notices in a structured format, which improves efficiency, reduces errors, and speeds up transaction processing. By using EDI, businesses can automate their communications and streamline their operations.

Following are different classifications of EDI's

1. Direct EDI

• Direct exchanges between trading partners without intermediaries.

2. EDI via Value-Added Network (VAN)

• A third-party service for document exchange, providing additional features like encryption and data translation and/or
• Outsourced services where a provider handles all aspects of EDI operations for a business.

3. Web-Based EDI

• Accessing EDI services through a web portal, allowing users to upload and download documents easily and/or
• EDI solutions hosted in the cloud, providing scalability and reduced IT infrastructure needs.

4. API-Based EDI

• Utilizes application programming interfaces for real-time data exchange, suitable for modern applications and e-commerce and/or
• Uses file transfer protocols (FTP/SFTP) for sending and receiving EDI documents securely.

Following are the key EDI systems in Syensqo along with the type of EDI

EDI based on the transactions

Assumptions

Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited. 

Constraints

Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.

Impacts

Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.

From sales process perspective, Syensqo currently send a number of major customers e-invoices via Elemica to Tungsten. (Route = SAP invoice > Webmethods > Elemica > Tungsten > Customer.) Examples here are P&G, Mondelez & Unilever. Elemica hold the contract the for this process and therefore, any changes to the EDI provider needs to take both the contract and EDI connection into consideration. 

Business Rules

The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order". 

Options considered

List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.

Option A: Option Title

Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option B: Option Title

Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option C: Option Title

Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option D: Option Title

Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Evaluation

Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.

	Option A	Option B	Option C	Option D
Criterion 1	Pro Con	Pro Pro	Pro Con	Pro Con
Criterion 2	Pro Con	Con	Pro Pro	Con Con
Criterion 3	Pro	Con	Con	Pro

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history