Skip to Content
0

How to handle VICS versions in SAP PO B2B addon

Aug 21, 2017 at 12:56 PM

87

avatar image
Former Member

We are getting EDI 850 ANSI X12 order from customer With version 004030VICS:- in ISA and GS segment. In sap b2b addon i do not see any version with 004030VICS. i do see 004030 version. Can youplease help me how to handle this inbounc EDI 850 document.

ISA*00* *00* *01*157322333 *01*7899951111 *170522*1430*^*00403*000000804*0*P*>~ GS*PO*157322333*7899951111*20170522*1430*000000804*X*004030VICS~ Normal EDI order with 004030 version:- When i get the doc with below values i am able to do the mapping and post the orders to SAPISA*00* *00* *01*157322333 *01*7899951111 *170522*1430*^*00403*000000804*0*P*>~ GS*PO*157322333*7899951111*20170522*1430*000000804*X*004030~

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Raghuraman S Aug 21, 2017 at 02:46 PM
0

You need to copy the control key In B2B cockpit.

Share
10 |10000 characters needed characters left characters exceeded
Manoj K Aug 21, 2017 at 01:17 PM
0

Hi Sankar,

What difference do you see between these 2 versions ?

You can actually copy the 00430 version from SAP control key to the custom create control key modify this version accordingly i.e add /modify /delete the fields in the structure accordingly and assign this control key to your scenario.

Here is one of the example.

Br,

Manoj

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Thank you Manoj for the information. I do not have any changes in structure level. Everything looks similar. Only need to create the new version: 004030VICS by copying near version in SAPB2B add on: 004030. I have gone trough couple of below blogs. My doubt is do i need to change anything in B2B tables as i am not updating any segment or field etc. I just need to create new version 004030VICS. I appreciate your help.

https://blogs.sap.com/2014/02/23/b2b-scenario-creating-and-testing-custom-edi-message-version-ansi-x12-855v2000/ https://blogs.sap.com/2016/03/23/working-with-customized-ansi-x12-messages/ https://blogs.sap.com/2014/02/04/getting-stuck-generating-edi-message-versions-less-than-002003-in-b2bic/

0

Sankar,

When there is no change why do you want to copy the same version and have a duplicate version of the same , whats the reason ? Usually you copy when you dont have the exact structure you need and then modify the copied version . SAP doesn't recommend to modify the tables manually , the tables are auto-generated when you import the B2B content or create a new Structure.

Br,

Manoj

0
avatar image
Former Member Aug 21, 2017 at 01:50 PM
0

Hi Manoj,

I am getting in the EDI file: GS*PO*157322333*7899951111*20170522*1430*000000804*X*004030VICS~. Its giving error at adapter level and also when i did content conversion as attached.errorwhileconvertinginb2ci.png. Also i might need to add fields in the future. Thank you manoj.


Share
10 |10000 characters needed characters left characters exceeded
Manoj K Aug 22, 2017 at 09:50 AM
0

Hi Sankar,

Try this :

1. Copy Control Key of message version 004030 of 850 into new control key with message version 004030VICS of 850 like below :

2. Now under Control key association link this control key with you interface by giving your interface details in below i have given my sender component.

3.Now go back to ANSX12 to XML converter convert the file using your custom created control key:

Br,

Manoj


850.png (57.9 kB)
control.png (23.1 kB)
anx12.png (124.0 kB)
Share
10 |10000 characters needed characters left characters exceeded