Step-by-step instructional guide for the RosettaNet implementation:
Objective: 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: // Connect with Rajat To take details as its not opening in Training Envirement
SAS_SAMSUNG_3A4R_IB_FileEvent: For 3A4R transaction.
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
This transaction is to process Rosettanet Samsung 3A4R
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".
"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.
Select Source “LAN”
Select Yes for convert the source
Select On File Created event trigger to transfer data.
Select the File event “SAS_SAMSUNG_3A4R_IB_FileEvent”
Select Source data format as XML and source data layout “SAS_SAMSUNG_3A4R_XMLLayout”
Select the Destinations Type as “LAN”
| Info |
|---|
Source Location for 3A4R: |
Select “Create File” to deliver data to destination.
Define the Intermediates Target as LAN File Target “Diodes_Intermediates_eVID_FileTarget”
| Info |
|---|
Location for Inbound Intermediate: |
12, Define target data format “Advanced Positional” and Define the target data layout
Define and Select Mapping and Save and Exit // Connect with Rajat To take details as its not opening in Training Envirement
2.b. Inbound Tr4ansation: SAS_SAMSUNG_3C4_IB
Inbound Transaction: SAS_SAMSUNG_3C4_IB
Define Network and Partner
"Transaction Settings" configuration interface with the following details:
Define Source “LAN”
| Info |
|---|
Source Location for 3C4: |
Select Yes for convert the source
On File Created event trigger to transfer data.
Select the File event “SAS_SAMSUNG_3C4_IB_FileEvent”
Select Source data format as XML and source data layout “SAS_SAMSUNG_3C4_XMLLayout
Select the Destinations Type as “LAN
Select “Create File” to deliver data to destination.
Define the Intermediates Target as LAN File Target “Diodes_Intermediates_eVID_FileTarget
12, Define target data format “Advanced Positional” and Define the target data layout
13. Define and Select Mapping and Save and Exit // Connect with Rajat To take details as its not opening in Training Envirement
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: DIODES_EDI_Inbound_PostProcess
Function: Archives files from the intermediate location and transfers them to the EVIB location (Oracle).
Steps:
Start Event
Purpose: Initiates the workflow process.
Details: The start event triggers the workflow to begin handling the inbound output file.
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.
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_ExtensionRemovalservice strips any extension from the file name, if applicable.Output: The file, now without an extension, is prepared for archiving.
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.
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.
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:
| Info |
|---|
Source Locations: Intermediate Location: Outbound Intermediate: |
4.a. Outbound Transaction : SAS_SAMSUNG_3A4C_OB
This transaction is to process Rosettanet Samsung 3A4C
Define Network and Partner
"Transaction Settings" configuration interface with the following details with in below screenshots.
.4 Select Source “LAN”
. Select Yes for convert the source
Select On File Created event trigger to transfer data.
7. Select the File event “SAS_SAMSUNG_3A4C_FileEvent”
8. Select Source data format as Advance Positional and source data layout
Select the Destinations Type as “Post Process”
Select Post Process Type, Process Flow and Parameters.
Define the Target Layout, Format as XML and Target data layout.
Define and Select Mapping and Save and Exit
4.b. Outbound Transaction : SAS_SAMSUNG_3C3_OB
This transaction is to process Rosettanet Samsung 3C3
Define and Select Network and Partner.
"Transaction Settings" configuration interface with the following details shown below screenshot:
4. Select Source “LAN”
5. Select Yes for convert the source
Select On File Created event trigger to transfer data.
Select the File event “SAS_SAMSUNG_3C3_FileEvent”
Select Source data format as Advance Positional and source data layout
Select the Destinations Type as “Post Process”
Select Post Process Type, Process Flow and Parameters.
Define and Select Mapping and Save and Exit
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).
Post Process:
Process Name: SAS_PF_SAMSUNG_OB
Function: Removes XML Encoding Header from outbound files.
he process flow illustrates :
Start Event: The process begins here, indicating the initiation of the workflow.
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.
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.
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.
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.
5. Process Flow Overview
Inbound Process Flow:
Place the source file in the source location.
After 3 minutes of polling frequency, the appropriate inbound transaction is executed.
The target file is placed in both the intermediate and archive locations.
After 2 minutes, the inbound post-process executes, transferring the target file from the intermediate to the EVIB location.
Outbound Process Flow:
Place the source file in the Oracle EVOB location.
After 3 minutes of polling frequency, the outbound pre-process executes.
The process archives the source file and transfers it to the intermediate location.
Based on the input criteria, the outbound transaction is executed, and the target file is placed in the
LexiCom/outbox/SAMSUNG_RNIFlocation.
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.
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.
This guide provides a detailed walkthrough of configuring and managing the RosettaNet transactions involving Samsung and DIODES SAS. If you need this document in a specific format or further clarifications, please let me know!
4o