The vendor just responded that the zeros are still not padded with the above fix.
Regards
Kalyan.
↧
Re: Correct padding for ISA13 and IEA02 in X12
↧
Re: Sender Mail Adapter - Channel Not Initialized
The URL was wrong, after confirming with basis the channel is working fine.
Thanks.
Nidhi
↧
↧
Re: B2B Monitoring View and Functional Profile Issue
Looks like your user does not have the Authorization to create and activte the Value Mapping.
You can find the details of the exception in nwa/logs.
While you are making the changes in the Administration screen, it will create Value Mappings 
Please verifiy the same.
Thanks,
Appala
↧
Re: B2B Monitoring View and Functional Profile Issue
Thanks Appala, it was in my changelist with this name.
Activating this works as expected.
Thanks,
Nidhi Srivastava
↧
SAP PI B2B Add-On - X.400 to Telekom
Hello All,
I am at the moment trying to connect to Telekom via X.400 with SAP B2B Add-On.
Can anybody confirm this is possible, i am not finding the general connect informations like Host and Port.
Our old System was connected through the Software FileWorks direktly from telekom, Overall X400 infos are quite rare.
Thanks and BR
Markus
↧
↧
Re: Status IDoc back for all outbound transactions
Issue resolved.
Status 8 --> Changes in ECC program
Status 7 --> Alert mail triggered for mapping error, IDOC number is coming in the mail. With that email an interface is created as -- Mail to Status Idoc which generates status 7 for the original IDoc.
Thanks,
Nidhi
↧
Re: Party,Business System & EDISeparator in B2B Scenarios
Hi Experts,
Can you please confirm on my conclusion, is there any risk in this approach?
Thanks,
Nidhi
↧
Re: OutboundRA - Error in Receiver IDoc Channel
Hi Experts,
Still unable to find the solution. Any inputs will be helpful.
Thanks,
Nidhi
↧
Re: Party,Business System & EDISeparator in B2B Scenarios
Hi Nidhi,
you do not need a party for inbound communications. However you will need to distinguish between different inbound communication partners - so:
I recommend to use party in inbound and outbound communications.
Why?
- You have an easier monitoring within PO.
- You can use TPM for inbound and outbound communication.
- You set up an internal standard for these integration patterns.
Kind regards,
Konrad
↧
↧
Re: SAP PI B2B Add-On - X.400 to Telekom
Hi Markus,
yes it is possible and working fine.
Make sure you have downloaded the correct and up to date certificate from the Telekom support website: www.service-viat.de
Standard connecting parameters are:
host: securep7.telebox400.de
port: 5432
Presentation Selector: OMSPSAP
Session Selector: SOMS_OSI_SERVER
Transport Selector: TOMS_OSI_SERVER
In processing tab the administrative domain must be viaT
Other connecting parameters you get from the Telekom (your own credentials, passwords) and from your EDI partners.
Make sure you use bodypart type IA5 text to keep your special characters.
By the way: It is also possible to connect via AS2 or OFTP2 to the viaT server. You need to ask viaT for the connecting parameters.
Kind regards
Konrad
↧
Re: Correct padding for ISA13 and IEA02 in X12
Hi Kalyan,
you can use the ArchiverModuleBean to get your final payload: Configuring the Communication Channel with Archiver Module - SAP NetWeaver Process Integration, business-to-business add…
For my scenarios the fix with the formatted value length is working fine. Please share your configuration with us.
Kind regards
Konrad
↧
line length limit for receiver vda file
Hello,
We have idoc to vda integration. The length of a vda file must be divisible by 128.
Also the each line must be 128 length or fewer in vda file.
We use idoc sender adapter and file receiver adapter.
In file receiver adapter we use module configuration
localejbs/VdaConverterModule (for xml to vda convert)
How can we configure module parameters for configuration of each line length?
Regards,
Nurhan
↧
Re: Party,Business System & EDISeparator in B2B Scenarios
Hi Nidhi,
For inbound cases we need to create two ICO's the flow will be
partner--->EDI receiver (files get splitted based on ST segments)
EDI sender----> ECC( IDoc's will be posted)
in order to post the IDOC's than we need to maintain partner profiles in ECC and that corresponding value should be mapped in PI
↧
↧
Re: Correct padding for ISA13 and IEA02 in X12
Hi kalyan,
Good day !! when i have started working with this NRO i have Also faced same issue you need to add format length as "9" that is enough for example if ISA control number 2 than the output in EDI file will be 000000002
Regards
Shiva
↧
Re: Party,Business System & EDISeparator in B2B Scenarios
Hi Nidhi,
kindly refer the below link for sample b2b scenario.
↧
Re: line length limit for receiver vda file
Hi Nurhan,
the VdaConverterModule always creates VDA files with a line length of 128.
See also these links:
Usually the module parameter vda.indent true/false helps.
However in some projects EDI partners send messages with a VDA length of 126 - columns 127 and 128 are in these case CRLF. In this case I used two MessageTransformBeans in the module chain to create a valid VDA message.
In a case you need to send a "VDA message" with a line length less than 128, you might consider using file content conversion (via MessageTransformBean) on the VDA-XML message or experimenting with the vda.trimWhitespaces module parameter (available with b2b addon SP04).
Kind regards
Konrad
↧
No ruleset for Control key/Message Type/Message version/Message sub version: -1/ORDERS/96A/000000 available in table B2B_EDI_CTRL_MSG
Dear ladies and gentlemen,
unfortunately we got the above error message back, if we try to send a AS2 EDIFACT Message va Mendelson Opensource AS2.
I haven't any idea, because the ruleset 1/ORDERS/96A/000000 is available, as well the Control Key Scenario Association.
Or is the "-" bfore the 1 wrong, if yes, how can I eleminate this sign...
So, I hope someone can help to solve this issue.
Thanks in advanced.
Kind regards
Stephan
↧
↧
Seeburger to SAP B2B addon
Hello Experts,
we are planning to migrate to Po , can somebody please help me to understand below quires:
1.We currently have interface where we are receiving/sending EDI file through Seeburger AS2 adapter, now as we are planning to migrate to PO and use SAP B2B Addon can some body let me know how do we need to migrate these interfaces i.e inbound as well as outbound with/without functional ack?if they have to build completely please let me know how do i need to configure these SAP Add-on for inbound and interface
2. We have few java mapping , if i am not wrong we just need to re-compile their would be no change in code right ?\
3. What about UDF does they cause any issues ?
Thanks in advance
Kiran
↧
Re: Seeburger to SAP B2B addon
↧
Re: Seeburger to SAP B2B addon
Hi Kiran,
for point 1 xsd structure may have change, not much experience here as we just plan to implement b2b addon in the future
for point 2 you will need to recompile with the correct java version, testing needed to validate(safety mesure)
for point 3 so far I have not seen any issues while migrating from PI to PO yet this is not the norm
Regards,
Gilbert A.
↧