on 2016 Dec 06 9:41 AM
Hi All,
The scenario I am trying to build is Invoice 880 Version 6020 from SOAP to EDI Separator and then from EDI Separator to File.
I have loaded B2B Content SP04 PAT03 (latest at the time of posting this question) into EDI Content Manager.
When I run the scenario without ticking 'Read from Dynamic Headers', the scenario works fine. However, when the option is ticked then the error occurs. Control Key Scenario Association is also filled with the default value of Control Key name SAP and .* as every other value.
Please let me know your thoughts. Thank you.
Kind regards,
Bala
Request clarification before answering.
Hi Bala,
ticking the checkbox "Read from Dynamic Headers" means that you must maintain the Trading Partner Management functionality. A short blog you fill find here: TPM Blog Part 1.
However you do not need to maintain TPM for working scenarios. Most of my scenarios are running fine without TPM. TPM is only maintained if it is part of a global integration concept.
Kind regards
Konrad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Konrad, for your inputs.
As you said, TPM is maintained for global access. As far as I know, acknowledgement settings can be set using this
'Read from Dynamic Headers' option. I have created two partners created with an agreement having 880 message in it.
As I understand from Part 5 of blog you shared, an agreement is required to select ControlKey during runtime.
Please see image below:
I read Trading Partner Management Part 6 - TPM Runtime Access of blog you shared. However, settings in that blog did not help.
What could be wrong with my scenario that hinders getting ControlKey.
Kind regards,
Bala
Hi Bala,
Along with what Konrad has shared I would also add that you want to pay attention to your acknowledgement settings. We recently updated our patch level on B2B and noticed these errors when the system tried to generate a 997 acknowledgement even for an incoming 997. If we did not have an appropriate EDI separator sender channel then the system would complain because it could not find a proper sender for the acknowledgement it was trying to send. Be sure that you have all necessary EDI separator sender channels created and active in your integration directory.
Regards,
Ryan Crosby
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
11 | |
9 | |
8 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.