/
RosettaNet Implementation

RosettaNet Implementation

Owned by Rajeev Rai (Deactivated)
Last updated: Sept 03, 2024

Step-by-step instructional guide for the RosettaNet implementation:

Implement RosettaNet standards for transaction sets involving Samsung as a partner in the DIODES SAS network.

Components:

  • Inbound Transactions: 3A4R (Purchase Order Request), 3C4 (Customization)

  • Outbound Transactions: 3A4C (Purchase Order Confirmation), 3C3 (Additional Outbound)

1. Network and Partner Configurations

  • Network: DIODES SAS

  • Partner: SAMSUNG (Non-EDI)

  • Target File Naming: Configured at the partner level to manage file names dynamically for each transaction set.

    • 3C3TargetFileName

    • 3C4TargetFileName

    • 3A4CTargetFileName

    • 3A4RTargetFileName

2. Inbound Events and Transactions:

  • Events:

    1. SAS_SAMSUNG_3A4R_IB_FileEvent: For 3A4R transaction.

    2. SAS_SAMSUNG_3C4_IB_FileEvent: For 3C4 transaction.

  • Inbound Transaction

a. SAS_SAMSUNG_3A4R_IB

b. SAS_SAMSUNG_3C4_IB

2.a. Inbound Transaction: SAS_SAMSUNG_3A4R_IB

  1. This transaction is to process Rosettanet Samsung 3A4R

image-20240830-061017.png

  1. The transaction is set to be used by a partner.

  • Select network "DIODES SAS".

  • select partner "SAS_SAMSUNG_RNIF".

  • These settings seem to be part of configuring a Rosettanet or similar business transaction. The partner configuration is associated with the network "DIODES SAS" and the partner "SAS_SAMSUNG_RNIF".

image-20240830-061527.png

  1. "Transaction Settings" configuration interface with the following details:

  • Contact User: This is the email address of the contact user for the transaction.

  • Notification Preference:

    • When to notify the contact user thru email?: The "Always" option is selected, meaning the contact user will be notified via email for all relevant events.

  • Email Notification Format: The format is set to "Default".

  • Data Encoding: This setting is displayed, but no specific encoding is selected in the visible part of the image.

These settings are part of the transaction configuration process, where the user specifies how and when notifications are sent and selects the data encoding format.

image-20240830-062627.png
image-20240830-062734.png

  1. Select Source “LAN”

image-20240830-063220.png

  1. Select Yes for convert the source

image-20240830-063340.png

  1. Select On File Created event trigger to transfer data.

image-20240830-063434.png

  1. Select the File event “SAS_SAMSUNG_3A4R_IB_FileEvent”

image-20240830-063521.png

  1. Select Source data format as XML and source data layout “SAS_SAMSUNG_3A4R_XMLLayout”

image-20240830-063607.png

  1. Select the Destinations Type as “LAN”

Source Location for 3A4R: \\LexiCom\inbox\SAMSUNG_RNIF\3A4_V02.00

image-20240830-063701.png

  1. Select “Create File” to deliver data to destination.

image-20240830-063747.png

  1. Define the Intermediates Target as LAN File Target “Diodes_Intermediates_eVID_FileTarget”

Location for Inbound Intermediate: EDI_IB_INTERMEDIATE

image-20240830-063829.png

12, Define target data format “Advanced Positional” and Define the target data layout

image-20240830-063914.png

  1. Define and Select Mapping and Save and Exit

image-20240830-064110.png

13.1 Data Mapping

image-20240903-104132.png

Mapping Details

Source Structure

  • Source: w:pip (DI_XMSC_RosettaNet_3A4R)

    • This is the source data structure named w:pip with the schema DI_XMSC_RosettaNet_3A4R.

    • It contains several elements and attributes such as @actionType, @host, @mailbox, @pipCode, @pipInstanceId, @pipVersion, @test, and nested structures like w:serviceContent.

    • Nested Structure:

      • w:serviceContent:

        • Contains a Pip3A4PurchaseOrderRequest element that includes:

          • fromRole: Information about the sender.

          • PurchaseOrder: Details about the purchase order.

          • thisDocumentGenerationDateTime: Timestamp for document generation.

          • thisDocumentIdentifier: Unique identifier for the document.

          • toRole: Information about the receiver.

Destination Structure

  • Destination: Root (Oracle_POI)

    • The destination structure is named Root with a schema called Oracle_POI.

    • It consists of various required fields like RecordNumber_0010-0010, RecordNumber_1000-1000, RecordNumber_1010-1010, and so on, which are placeholders for different data points that need to be mapped from the source.

 

2.b. Inbound Tr4ansation: SAS_SAMSUNG_3C4_IB

  1. Inbound Transaction: SAS_SAMSUNG_3C4_IB

image-20240830-091541.png

  1. Define Network and Partner

image-20240830-091827.png

  1. "Transaction Settings" configuration interface with the following details:

image-20240830-091920.png
image-20240830-092000.png
image-20240830-092046.png

  1. Define Source “LAN”

Source Location for 3C4: \\LexiCom\inbox\SAMSUNG_RNIF\3C4_V01.00

image-20240830-092136.png

  1. Select Yes for convert the source

image-20240830-092210.png

  1. On File Created event trigger to transfer data.

image-20240830-092255.png

  1. Select the File event “SAS_SAMSUNG_3C4_IB_FileEvent”

image-20240830-092330.png

  1. Select Source data format as XML and source data layout “SAS_SAMSUNG_3C4_XMLLayout

image-20240830-092419.png

  1. Select the Destinations Type as “LAN

image-20240830-092515.png

  1. Select “Create File” to deliver data to destination.

image-20240830-092554.png

  1. Define the Intermediates Target as LAN File Target “Diodes_Intermediates_eVID_FileTarget

image-20240830-092631.png

12, Define target data format “Advanced Positional” and Define the target data layout

image-20240830-092713.png

13. Define and Select Mapping and Save and Exit // Connect with Rajat To take details as its not opening in Training Envirement

image-20240830-093127.png

 

 

 

image-20240903-104815.png

Mapping Details:

Source Structure

  • Source: w:pip (DI_XMSC_RosettaNet_3A4R)

    • The source structure is named w:pip and follows the DI_XMSC_RosettaNet_3A4R schema.

    • It contains several attributes and nested structures:

      • Attributes include @actionType, @host, @mailbox, @pipCode, @pipInstanceId, @pipVersion, and @test.

      • Nested Structure: w:serviceContent

        • Contains Pip3C4InvoiceRejectNotification, which includes elements such as:

          • fromRole: Contains information about the sender's role.

          • GlobalDocumentFunctionCode: The function code related to the document.

          • Invoice: Details of the invoice.

          • requestingDocumentDateTime: Date and time when the document was requested.

          • requestingDocumentIdentifier: A unique identifier for the requesting document.

          • thisDocumentGenerationDateTime: The generation date and time of the current document.

          • thisDocumentIdentifier: The unique identifier of the current document.

          • toRole: Contains information about the receiver's role.

Destination Structure

  • Destination: Root (SAS_SAMSUNG_3C4_ADPLayout)

    • The destination structure is named Root with the schema SAS_SAMSUNG_3C4_ADPLayout.

    • It contains a nested structure message_code_01_MESSAGE_CODE_-3C4, with fields such as:

      • message_code_01_MESSAGE_CODE_: Code representing the message.

      • Partner__02_PARTNER_: Represents the partner information.

      • EDI_location__03_EDI_LOCATION_: The EDI location associated with the message.

      • Out_identifier__04_OUT_IDENTIFIER_: Outbound identifier for the message.

      • Out_date__05_OUT_DATE_: Outbound date.

      • In_identifier__06_IN_IDENTIFIER_: Inbound identifier.

      • In_date__07_IN_DATE_: Inbound date.

      • Document_no__08_DOCUMENT_NO_: Document number.

      • Reject_code__09_REJECT_CODE_: Code indicating why a document was rejected.

      • Error_message__10_ERROR_MESSAGE_: A message indicating an error or rejection reason.

 

3. Inbound Post Process:

This workflow is designed to handle an inbound output file through a series of steps, including processing, archiving, and transferring the file to its final destination. The workflow ensures that the file is correctly processed and stored.

  • Process Name: DI_FE_Inbound_PostProcess

  • Function: Archives files from the intermediate location and transfers them to the EVIB location (Oracle).

image-20240903-064503.png

Steps:

  1. Start Event

    • Purpose: Initiates the workflow process.

    • Details: The start event triggers the workflow to begin handling the inbound output file.

  2. Inbound Output File Intermediate Location on evib

    • Purpose: The inbound output file is first placed in an intermediate location on the evib system.

    • Details:

      • Input: The file that needs to be processed.

      • Action: The file is received and stored temporarily at a designated intermediate location.

      • Output: The file is ready for further processing in the next step.

  3. Diodes_CP_ExtensionRemoval

    • Purpose: This step processes the file by removing any file extension if present.

    • Details:

      • Input: The file from the intermediate location.

      • Action: The Diodes_CP_ExtensionRemoval service strips any extension from the file name, if applicable.

      • Output: The file, now without an extension, is prepared for archiving.

  4. Inbound Output Archival

    • Purpose: The processed file is archived for future reference or recovery.

    • Details:

      • Input: The file with the extension removed.

      • Action: The file is stored in an archival system. This ensures that a backup of the file is maintained.

      • Output: The file is securely archived and ready for the next step in the workflow.

  5. Inbound evib File Target

    • Purpose: The file is moved to its final target location within the evib system.

    • Details:

      • Input: The archived file.

      • Action: The file is transferred to its designated target location within the evib system.

      • Output: The file reaches its final destination.

  6. End Event

    • Purpose: The workflow concludes after the file has been successfully processed and moved to its target location.

    • Details: The end event signifies the successful completion of the workflow.

This workflow ensures that an inbound output file is carefully processed, archived, and delivered to its final location within the evib system. Each step in the process is critical for ensuring the integrity and availability of the file.

4. Outbound Transactions

Outbound Events and Transactions:

  • Events:

    • SAS_SAMSUNG_3A4C_FileEvent

    • SAS_SAMSUNG_3C3_FileEvent

  • Inbound Transaction

a. SAS_SAMSUNG_3A4C_OB

b. SAS_SAMSUNG_3C3_OB

Source Locations: ORACLE evob

Intermediate Location: Outbound Intermediate: EDI_OB_INTERMEDIATE

4.a. Outbound Transaction : SAS_SAMSUNG_3A4C_OB

  1. This transaction is to process Rosettanet Samsung 3A4C

image-20240901-070655.png

  1. Define Network and Partner

image-20240901-070811.png

  1. "Transaction Settings" configuration interface with the following details with in below screenshots.

image-20240901-070900.png
image-20240901-070929.png

.4 Select Source “LAN”

image-20240901-071013.png

  1. . Select Yes for convert the source

image-20240901-071050.png

  1. Select On File Created event trigger to transfer data.

image-20240901-071122.png

7. Select the File event “SAS_SAMSUNG_3A4C_FileEvent”

image-20240901-071228.png

8. Select Source data format as Advance Positional and source data layout

image-20240901-071305.png

  1. Select the Destinations Type as “Post Process”

image-20240901-071410.png

  1. Select Post Process Type, Process Flow and Parameters.

image-20240901-071507.png

  1. Define the Target Layout, Format as XML and Target data layout.

image-20240901-071540.png

  1. Define and Select Mapping and Save and Exit

image-20240901-071624.png

12.1 Data Mapping

image-20240903-110924.png

Data Mapping Details

1. Source Structure

  • Record Numbers: These represent different records or data fields that are part of the source dataset. Each RecordNumber could represent a specific piece of information that needs to be mapped to a corresponding field in the destination structure.

    • RecordNumber_1120-1120

    • RecordNumber_1130-1130

    • RecordNumber_1200-1200

    • ...

    • RecordNumber_1420-1420

2. Destination Structure (w:pip (SAS_SAMSUNG_3A4C_XMLLayout))

  • Attributes:

    • @actionType (M)

    • @pipCode (M)

    • @pipInstanceId (M)

    • @test (M)

  • Elements:

    • w:serviceContent

      • Pip3A4PurchaseOrderConfirmation

        • fromRole: Specifies the role of the sender.

        • GlobalDocumentFunctionCode: Code that identifies the function of the document.

        • PurchaseOrder: Contains details of the purchase order.

        • requestingDocumentDateTime: Date and time when the document is requested.

        • requestingDocumentIdentifier: Unique identifier for the requested document.

        • thisDocumentGenerationDateTime: Date and time when the document was generated.

        • thisDocumentIdentifier: Unique identifier for the current document.

        • toRole: Specifies the role of the receiver.

4.b. Outbound Transaction : SAS_SAMSUNG_3C3_OB

  1. This transaction is to process Rosettanet Samsung 3C3

image-20240901-071807.png

  1. Define and Select Network and Partner.

image-20240901-071922.png

  1. "Transaction Settings" configuration interface with the following details shown below screenshot:

image-20240901-071953.png
image-20240901-072037.png

4. Select Source “LAN”

image-20240901-072107.png

5. Select Yes for convert the source

image-20240901-072135.png

  1. Select On File Created event trigger to transfer data.

image-20240901-072203.png

  1. Select the File event “SAS_SAMSUNG_3C3_FileEvent”

image-20240901-072238.png

  1. Select Source data format as Advance Positional and source data layout

image-20240901-072305.png

  1. Select the Destinations Type as “Post Process”

image-20240901-072351.png

  1. Select Post Process Type, Process Flow and Parameters.

image-20240901-072426.png

  1. Define and Select Mapping and Save and Exit

image-20240901-072524.png

12.1 Data Moping

image-20240903-111732.png

Data Mapping Details

1. Source Structure

  • Record Numbers: These represent the fields or records from the source data that need to be mapped to the destination. The records include:

    • RecordNumber_1000-1000

    • RecordNumber_1010-1010

    • RecordNumber_1015-1015

    • RecordNumber_1030-1030

    • RecordNumber_1032-1032

    • RecordNumber_1034-1034

    • RecordNumber_2000-2000

    • RecordNumber_2010-2010

    • RecordNumber_2100-2100

    • RecordNumber_2110-2110

    • RecordNumber_2200-2200

    • RecordNumber_2210-2210

    • RecordNumber_2300-2300

    • RecordNumber_2310-2310

    • RecordNumber_2400-2400

    • RecordNumber_2410-2410

2. Destination Structure (w:pip (SAS_SAMSUNG_3C3_XMLLayout))

  • Attributes:

    • @pipCode (M): Mandatory attribute representing the PIP (Process Integration Profile) code.

    • @test (M): Mandatory attribute indicating if the current instance is in test mode.

  • Elements:

    • w:serviceContent

      • Pip3C3InvoiceNotification

        • fromRole: The role of the sender in the invoice process.

        • GlobalDocumentFunctionCode (M): Mandatory field that represents the function code of the document.

        • Invoice: Contains invoice details.

        • thisDocumentGenerationDateTime: The date and time when the document was generated.

        • thisDocumentIdentifier: A unique identifier for the current document.

        • toRole: The role of the receiver in the invoice process.

5. Outbound Pre Process:

  • Process Name: DIODES_EDI_Outbound_Preprocess

  • Function: Archives the source file and moves it to the intermediate location. Handles file splitting based on the Purchase Order number (Key 1).

5.a. Outbound Post Process:

  • Process Name: SAS_PF_SAMSUNG_OB

  • Function: Removes XML Encoding Header from outbound files.

image-20240901-065423.png

he process flow illustrates :

  1. Start Event: The process begins here, indicating the initiation of the workflow.

  2. Dummy LAN File Source: This step represents the source of the data. It is labeled as a "Dummy LAN File Source," suggesting that this is a placeholder or test data source in a Local Area Network (LAN) environment. The data is fetched or initiated from this source to proceed further in the flow.

  3. Custom Code to Remove XML Encoding Header: In this step, custom code is applied to modify the data. Specifically, the code removes the XML encoding header from the data. This is likely a necessary preprocessing step to ensure that the data is in the correct format or to comply with downstream system requirements.

  4. Samsung Outbound LAN File Target: After the data has been processed (i.e., the XML encoding header is removed), it is sent to the "Samsung Outbound LAN File Target." This step represents the destination where the processed data is stored or transmitted over the LAN to a Samsung-related system or endpoint.

  5. End Event: This marks the completion of the process flow. Once the data reaches the Samsung Outbound LAN File Target, the workflow is considered complete.

This process flow is part of a data transformation or transmission setup where data is prepared and formatted correctly for delivery to a specific target system.

6. Mail Notifications

  • Configuration: Mail notifications are set up at the transaction level.

  • Purpose: Provides alerts for any transaction failures to ensure timely responses and corrections.

image-20240903-095519.png

Below is the snapshot of how a mail notification will be received in case of any failure.

image-20240903-095555.png

7. Post-Deployment Actions

  • Adjust File Events: Update file events and source locations as needed.

  • Target Location Updates: Modify target location activities based on the requirements of each transaction set.

3A4R - INBOUND

3A4R is a purchase Order Request.

Transaction Name- SAS_SAMSUNG_3A4R_IB

Source Layout- SAS_SAMSUNG_3A4R_XMLLayout (XML)

Destination Layout- Oracle POI(Advanced Positional)

File Event- SAS_SAMSUNG_3A4R_IB_FileEvent

Source file gets picked up from \\dac2devtsbap2.diodes.com\LexiCom\inbox\SAMSUNG_RNIF\3A4_V02.00.

●      Create a new file Event with your Suitable source location

image-20240903-095939.png

●      Create a new target location activity in transaction

3A4C - OUTBOUND

3A4C is purchase order confirmation. It is sent as a confirmation to 3A4R.

Transaction Name- SAS_SAMSUNG_3A4C_OB

Source Layout- Oracle_POAO

Destination Layout- SAS_SAMSUNG_3A4C_XMLLayout

File Event- SAS_SAMSUNG_3A4C_FileEvent

Mapping Name- SAS_SAMUSNG_3A4C_V2_Mapping

Source file gets picked up from the evob folder.

Create a new file Event with your Suitable source location

Create a new target location activity in transaction

Source file of 3A4C can contain multiple PO requests. To handle the scenario, the 3A4C source file gets splitted based on Key 1( Purchase order Number). It is implemented at the outbound preprocess level where we are splitting the source file based on the naming convention (*SS3A4C*) , archiving the source files and transferring the splitted files to EDI_OB_INTERMEDIATE location.

3C4 - INBOUND

Transaction Name- SAS_SAMSUNG_3C4_IB

Source Layout- SAS_SAMSUNG_3C4_XMLLayout

Destination Layout- SAS_SAMSUNG_3C4_ADPLayout

FileEvent- SAS_SAMSUNG_3C4_IB_FileEvent

Source file gets picked up from location- \\dac2devtsbap2.diodes.com\LexiCom\inbox\SAMSUNG_RNIF\3C4_V01.00

●      Create a new file Event with your Suitable source location

image-20240903-100106.png

●      Create a new target location activity in transaction

3C3 - OUTBOUND

Transaction Name- SAS_SAMSUNG_3C3_OB

Source Layout- SAS_SAMSUNG_3C3_ADPLLayout

Destination Layout- SAS_SAMSUNG_3C3_XMLLayout

FileEvent- SAS_SAMSUNG_3C3_FileEvent

Source file gets picked up from location- evob

Create a new file Event with your Suitable source location

Create a new target location activity in transaction

 File Include Criteria     

*SS3C3*