When an inbound 810 is received from the trading partner endpoint, a monitor picks up the file and an Event tries to find the matching inbound route. If found, the EDI message is translated to NetSuite Vendor Bill XML and then posted to NetSuite.
This section explains how to configure the integration to process the Inbound Invoice that is received from the Trading Partner and create the corresponding Standard Vendor Bill on NetSuite.
How to Configure
- Configure the Cloud Monitor: InboundEDIMN present in
com.cleo.b2bcloud.core
under the packagecom.cleo.b2bcloud.core.cloudMonitor
has to be configured with trading partner endpoint setup in CIC and the ReceiveEDIEvent is already configured in the Cloud Monitor to process further. - Configure the Inbound Route: Setup the Inbound Route with the Sender ID as Trading Partner name and Receiver ID as the customer name supplied in the Wizard properties file (“accelerator-input.properties” file under the “resources” folder). If there are changes, modify _TP_810v4010IR in the
com.cleo._customer_.netsuite._tp_.inbound.n810.v4010
package as required. - Configure the 997 Enveloper: The 997 envelope details and the trading partner endpoint to which the 997 is to be sent should be configured in _TP_997ENV in the trading partner project under
com.cleo._customer_.netsuite._tp_.outbound.n997
package.
How to Run the Flow
- Before proceeding, ensure that the following Projects have been deployed. If any of these Projects are already deployed and remain unmodified, there is no need to redeploy them. Similarly, if any of these Projects were not checked out to your Workspace, they can be skipped from the deployment process.
-
- com.cleo._customer_.edi
- com.cleo._customer_.booster.netsuite
- com.cleo._customer_.edinetsuite
- com.cleo._customer_.netsuite._tp_
- com.cleo.b2bcloud.core
- com.cleo.b2biaas.clarify
- com.cleo.cic.cockpit.core
- com.cleo.cic.cockpit.core.n810
- com.cleo.cic.cockpit.core.n850
- com.cleo.cic.cockpit.core.n855
- com.cleo.cic.cockpit.core.n856
- com.cleo.cic.connector.netsuite
- Configure the Exit Points as follows.
- Ensure that the Cloud Monitor com.cleo.b2bcloud.core.cloudMonitor.InboundEDIMN” is started. This can be done in Admin Console > Resource Monitors.
How to Monitor the Flow
- Monitor the flow using the following:
- Auditor log entries. See Using the CIC Studio Auditor for more information.
- Message Tiles
- Jobs
- Dashboard > Charts
- In case of errors:
- A ticket is generated and information is also visible in the Message and Job views in CIC Cockpit. Below are screenshots of Cockpit Tiles and Job displaying errors, respectively.
- If the Trading Partner configuration is not found, a ticket is created and also an optional email alert is generated.
- If the file fails to process due to invalid EDI syntaxes, a ticket is created, and rejected 997 is sent to the trading partner.
How to Customize
- Replace the custom fields in the ruleset with your own custom fields:
- If you have any custom fields in your NetSuite instance already, and you want to use them then the same has to be updated in the Ruleset.
- Look for the specific field mapping in the ruleset _TP_810v4010RS residing in the
com.cleo._customer_.netsuite._tp_.inbound.n810.v4010
package. The Cleo-specific custom field is mapped with custbody_cleo_<field id>. Change the same to reflect the corresponding field id.
- Add more details while creating the Vendor Bill on NetSuite or add specific business logic while creating the Vendor Bill on NetSuite
- The Vendor Bill on NetSuite is currently created with the required data to process orders successfully. Cleo-defined custom fields have been used to map specific values from the EDI files. The values that are being mapped are documented in the IDs Template P2P X12 <> NetSuite Mapping Spec P2P present in the docs folder under the
com.cleo._customer_.edinetsuite
project. However, if you wish to add any additional fields then the ruleset _TP_810v4010RS needs to be updated as per the requirement.
- The Vendor Bill on NetSuite is currently created with the required data to process orders successfully. Cleo-defined custom fields have been used to map specific values from the EDI files. The values that are being mapped are documented in the IDs Template P2P X12 <> NetSuite Mapping Spec P2P present in the docs folder under the
- Contact Cleo support if you need any assistance while adding additional rules.
Comments
0 comments
Please sign in to leave a comment.