Diode: Rosettanet Implementation

Owned by Rajeev Rai
Last updated: Sept 04, 2024
2 min read

Learning Objective:

  • Implementation: of Rosettanet protocols for B2B transactions between Diodes and SAMSUNG.

  • Protocol: Rosettanet, using XML-based message exchanges.

  • Automation: Handles both inbound and outbound purchase orders and confirmations.*(used Data Integration Pre Built Template)

  • File Management: Automatic file processing, archiving, and notifications integrated into the system.( On Error Notification)

  • Key Transactions: Inbound: Processes purchase order requests and other inbound documents. Outbound: Manages purchase order confirmations and other outbound documents.

  • System Integration: Notifications: Alerts system administrators in case of failures during transactions.

Key Use Case:

Context:
The use case revolves around automating transaction processes for Diodes and SAMSUNG through a Rosettanet compliant system. The system must handle four types of transactions (inbound and outbound) for purchase orders and confirmations.

Key Roles:

  • Diodes: The organization implementing Rosettanet.

  • SAMSUNG (Non-EDI): The business partner exchanging transactions.

  • System Administrators: Responsible for configuring the network, partner settings, and process flows.

Process Flows:

  1. Inbound Transactions: (Recive Roesetanet file from partner and converting into positional )

    • Triggered by placing a source file in the specified location.

    • Polling frequency checks for new files every 3 minutes.

    • Files are processed and moved to intermediate and archive locations.

  2. Outbound Transactions:(Sent File to partner from potional to rosatenet )

    • Triggered by placing a file in the Oracle evob location.

    • Files are archived, processed, and moved to the outbox after splitting by purchase order (PO) number.

    • Example: The 3A4C outbound transaction splits files based on PO numbers before processing.

Requirements:

  • Transaction Sets: (PIPs - Partner Interface Process)

    1. 3A4R (Inbound): Purchase order request from SAMSUNG to Diodes.

    2. 3A4C (Outbound): Purchase order confirmation from Diodes to SAMSUNG.

    3. 3C3 (Outbound): Customization/notification from Diodes to SAMSUNG.

    4. 3C4 (Inbound): Rejection notifications from SAMSUNG to Diodes.

  • File Handling:

    • Inbound Files: Must be archived and moved to intermediate and archival locations.

    • Outbound Files: Archived, split by PO number, and moved to specified directories.

Post-Deployment Activities:

  • File Events: New file events and locations are created based on the transaction type.

  • Mail Notifications: Integrated into the system to notify administrators of any failures during the transaction process.

Inbound Post Process

Outbound Pre Process for splitting 34AC file

This use case showcases an automated transaction management system using Rosettanet standards, improving the efficiency and accuracy of file-based B2B communications between Diodes and SAMSUNG​(Rosettanet Implementation…).