EDI 831 transaction

Hi All,
       I am working with F110(Automatic payment run) transaction for EDI 831 transaction. I need to create idocs whenever F110 transaction get's triggered. For that i found a program RFFOEDI1 program as payment medium program. But i dont't know how to use this program for my requirement and i have one more doubt that Some output type should be assigned or not to this trandaction(F110) for EDI processing.
        Please, can anyone suggest me about IDoc generation with F110 triggering and also pls tell is there any Output type for the transaction F110 for EDI processing.
         Please let me know ASAP.
Thanks in Advance.

Hi Rushali,
          Thank you for response. The answer you gave is fine. Actually i came to know that when we run the F110 transaction with RFFOEDI1 as the medium program,it will create two IDOCs one for payment adive and the other for remittance adveice both are of type PEXR2001 which is nothing but EDI 820 Transaction. But i need to get the summary IDOC(of type IDCREF01) of the above 820 transactions for 831 EDI transaction.
           I am not sure that the payment medium program RFFOEDI1 will create IDCREF01 IDOCs also. Please let me know how to get IDCREF01(summary idoc) for F110 run.
            Please give the feedback ASAP. Thank u very much in advance.

Similar Messages

Unable to retrieve inbound EDI X12 transactions from VAN using FTPS connect

When out B2B process is polling we do not seeing any attempts to connect to the ftp site. We have no problems putting EDI outbound transactions to the VAN with the same connection, but never see an attempt to get transactions. We enabled the transport trace logging, but are not seeing any connection information in this log file nor in the b2b.log file. Why would we be able to put files to the VAN but not pick up files with the same connection information?

If you enable the transport trace in tip.properties, you will see a log similar to the following:
TransportProperties.TransportProperties():http.receiver.instance_name=IP;PROTOCOL_ENDPOINT=null;file.receiver.password=******;file.receiver.wallet_location=C:\temp/ewallet.p12;file.receiver.user=ekhor;file.receiver.polling_interval=60;polling_interval=60;file.receiver.channel_mask=None;smtp.receiver.protocol=imap;file.sender.channel_mask=None;http.receiver.registry_port=5110;
TransportProperties.TransportProperties():http.receiver.registry_port=5110;port=1688;smtp.receiver.protocol=imap;PROTOCOL_ENDPOINT=null;http.receiver.instance_name=IP;
FileReceiver.init() started ....
FileReceiver.init() completed.
[IPT_HttpRecRegisterBegin] HTTPReceiver.init(): Registering HTTP Receiver ...
RMIResponsePort = null
Host name is 'dlsun1317'.
low port = 5110
high port = 5110
Host dlsun1317 FTP command: USER ekhor
FTP Command: USER, reply:
331 Password required for ekhor.
Host dlsun1317 FTP command: PASS
FTP Command: PASS, reply:
230 User ekhor logged in.
Host dlsun1317 FTP command: PASV
FTP Command: PASV, reply:
227 Entering Passive Mode (144,25,141,108,194,80)
Passive: ip = 144.25.141.108, port = 49744
Connecting to dlsun1317.us.oracle.com:49744
Host dlsun1317 FTP command: NLST //private/ekhor/Acme_endpoint
FTP Command: NLST, reply:
150 ASCII data connection for /bin/ls (144.25.142.57,3110) (0 bytes).
Disconnecting from dlsun1317
Host dlsun1317 disconnected.
Started Receiver at rmi port 5110.
[IPT_HttpRecRegisterCompleted] HTTPReceiver.init(): Completed registering HTTP Receiver.
FileSourceMonitor.prepareShutdown()
FileSourceMonitor.prepareShutdown() - done
The following flag needs to set in tip.properties:
oracle.tip.adapter.b2b.transportTrace=/tmp/transport.log
If you also want to display the password in transport.log (masked by ****** above)
you need to also set
oracle.tip.adapter.b2b.passwordTrace = true
It is possible to have the outbound FTP/S working while the inbound FTP/S is not. The reason is due to different configuration of delivery channels. In the outbound case, B2B uses the remote trading partner delivery channel information to login and to drop the file whereas B2B uses the host delivery channel information to login and to poll whether there are any files in the FTP/S server.
Please verify again that your host delivery channel and tip.properties settings are correct.
Thanks,
Eng

EDI X12 Transaction Sets

Hi,
I have a client that needs to import a variety of EDI document types (846, 852, 867), etc... I was looking at the B2B user guide and it stated that you can use the X12 transaction sets (850, 855 and 997) when you create a business action. Does that mean other document types cannot be defined as a business action? If they can be, what extra work would be required to define their formats, character sets, and data elements.
Thanks,
Thomas

Hello Thomas,
Oracle AS B2B supports any Document Type defined under X12/EDIFAC guidelines as long as you have the corresponding ecs file defined using B2B Document Editor. Transaction set referred in your post is any EDI compliant document which has to be part of the Envelope i.e Interchange/Group. HTH.
While defining the Document Type you might want to define metadata for the same. Please let me know or feel free to mail me for any specific question.
Rgds,Ramesh

Implementation of EDI Tradacoms transactions

Hi,
I am working on Oracle B2B. Currently, I am working on EDI-Tradacoms. I am using Documnent Editor 7.0.5 for generating test data. I tried to generate data for a order file(004 for TRADACOMS) from all sides but I am getting error as "Guideline Files Not Supported" always.
Can you please throw some light on this issue. Because of this problem, I could not proceed with Implementation of Tradacoms transactions in Oracle B2B.
Thanks,
Arnab

Anuj,
Thanks for your help.
To add to it, I would also like to mention that I have taken a sample tradacom order file from the net as
STX=ANAA:1+234567+5030670019458++1234++ORDHDR' MHD=1+ORDHDR:9' TYP=0430' SDT=5030670019458' CDT=:234567' FIL=1+1' MTR=6' MHD=2+ORDERS:9' CLO=::234567' ORD=ABC987' OLD=1+9780863475764+++1+4+++T' DNB=1+1++082:ABC987-1' OLD=2+:KMCD2723+++1+3+++N' DNB=2+1++082:ABC987-2' OTR=2' MTR=9' MHD=3+ORDTLR:9' OFT=1' MTR=3' MHD=4+RSGRSG:2' RSG=1234+5030670019458' MTR=3' END=4'
Now, when I used Data Analyzer to test this data with the sample guideline, I got a lot of errors as follows. Can you please throw somw light on this.
"#","Error ID","Error Message","Error Data","SNIP Type","Severity"
"1","0x81004F","Composite STX04 (Date and Time of Transmission) is missing. This Composite's standard option is 'Mandatory'. Segment STX is defined in the guideline at position N/A. This Composite was expected in: Segment Count: 1 Composite Count: 4 Character: 32 A composite data element with 'Mandatory' status is missing.","(N/A)","1 - EDI Syntax","Normal"
"2","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 2 Characters: 46 through 64 Validator error - Extra data was encountered."," MHD=1+ORDHDR:9","1 - EDI Syntax","Normal"
"3","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 3 Characters: 65 through 77 Validator error - Extra data was encountered."," TYP=0430","1 - EDI Syntax","Normal"
"4","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 4 Characters: 78 through 99 Validator error - Extra data was encountered."," SDT=5030670019458","1 - EDI Syntax","Normal"
"5","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 5 Characters: 100 through 115 Validator error - Extra data was encountered."," CDT=:234567","1 - EDI Syntax","Normal"
"6","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 6 Characters: 116 through 127 Validator error - Extra data was encountered."," FIL=1+1","1 - EDI Syntax","Normal"
"7","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 7 Characters: 128 through 137 Validator error - Extra data was encountered."," MTR=6","1 - EDI Syntax","Normal"
"8","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 8 Characters: 138 through 156 Validator error - Extra data was encountered."," MHD=2+ORDERS:9","1 - EDI Syntax","Normal"
"9","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 9 Characters: 157 through 173 Validator error - Extra data was encountered."," CLO=::234567","1 - EDI Syntax","Normal"
"10","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 10 Characters: 174 through 188 Validator error - Extra data was encountered."," ORD=ABC987","1 - EDI Syntax","Normal"
"11","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 11 Characters: 189 through 222 Validator error - Extra data was encountered."," OLD=1+9780863475764+++1+4+++T","1 - EDI Syntax","Normal"
"12","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 12 Characters: 223 through 248 Validator error - Extra data was encountered."," DNB=1+1++082:ABC987-1","1 - EDI Syntax","Normal"
"13","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 13 Characters: 249 through 278 Validator error - Extra data was encountered."," OLD=2+:KMCD2723+++1+3+++N","1 - EDI Syntax","Normal"
"14","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 14 Characters: 279 through 304 Validator error - Extra data was encountered."," DNB=2+1++082:ABC987-2","1 - EDI Syntax","Normal"
"15","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 15 Characters: 305 through 314 Validator error - Extra data was encountered."," OTR=2","1 - EDI Syntax","Normal"
"16","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 16 Characters: 315 through 324 Validator error - Extra data was encountered."," MTR=9","1 - EDI Syntax","Normal"
"17","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 17 Characters: 325 through 343 Validator error - Extra data was encountered."," MHD=3+ORDTLR:9","1 - EDI Syntax","Normal"
"18","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 18 Characters: 344 through 353 Validator error - Extra data was encountered."," OFT=1","1 - EDI Syntax","Normal"
"19","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 19 Characters: 354 through 363 Validator error - Extra data was encountered."," MTR=3","1 - EDI Syntax","Normal"
"20","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 20 Characters: 364 through 382 Validator error - Extra data was encountered."," MHD=4+RSGRSG:2","1 - EDI Syntax","Normal"
"21","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 21 Characters: 383 through 409 Validator error - Extra data was encountered."," RSG=1234+5030670019458","1 - EDI Syntax","Normal"
"22","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 22 Characters: 410 through 419 Validator error - Extra data was encountered."," MTR=3","1 - EDI Syntax","Normal"
"23","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 23 Characters: 420 through 429 Validator error - Extra data was encountered."," END=4","1 - EDI Syntax","Normal"
"24","0x810070","Unrecognized data was found in the data file. The last known Segment was STX at guideline position N/A. This error was detected at: Segment Count: 24 Characters: 430 through 432 Validator error - Extra data was encountered."," ","1 - EDI Syntax","Normal"
"25","0x2010001","The Transaction Trailer is missing. The segment itself may be missing or the Segment Delimiter may be missing. Trailer was expected after: Character: 432 Parser error - Missing trailer.",,"1 - EDI Syntax","Warning"
"26","0x810051","Loop ORDHDR (Order File Header) at guideline position 010 is missing. This Loop's standard option is 'Mandatory'. This Loop was expected after: Segment Count: 24 Character: 432 A data loop with 'Mandatory' status is missing.",,"1 - EDI Syntax","Normal"
"27","0x810051","Loop ORDERS (Order Details) at guideline position 080 is missing. This Loop's standard option is 'Mandatory'. This Loop was expected after: Segment Count: 24 Character: 432 A data loop with 'Mandatory' status is missing.",,"1 - EDI Syntax","Normal"
"28","0x810051","Loop ORDTLR (Order File Trailer) at guideline position 170 is missing. This Loop's standard option is 'Mandatory'. This Loop was expected after: Segment Count: 24 Character: 432 A data loop with 'Mandatory' status is missing.",,"1 - EDI Syntax","Normal"
"29","0x81004D","Segment END (End of Transmission) at guideline position N/A is missing. This Segment's standard option is 'Mandatory'. This Segment was expected after: Segment Count: 24 Character: 432 A data segment with 'Mandatory' status is missing.",,"1 - EDI Syntax","Normal"
"30","0x9310258","Message RSGRSG is missing in the transmission. It is expected to be sent when syntax identifier (STX01-01) has value 'ANAA'. Message RSGRSG is required.",,"1 - EDI Syntax","Normal"

EDI 810 transaction error: Cannot uniquely identify a trading partner

Hi,
I am facing following error on B2B 11g version 11.1.1.6.0. Please provide the solution if you are aware of the issue.
Error Description: Cannot uniquely identify a trading partner. The trading partners PARTNER-A, PARTNER-B have the same set of identifications.
Partner Identification parameter for PARTNER-A and PARTNER-B
EDI Interchange ID: xxxx
EDI Interchange ID Qualifier: yyyy
EDI Group ID: 111
Name: PARTNER-A
EDI Interchange ID: xxxx
EDI Interchange ID Qualifier: yyyy
EDI Group ID: 111
Name: PARTNER-B
Thank you
Ram

Two TPs can not have same identification.
There are two ways to come out of this problem.
1. Change the identification criteria for the TP.
2. Use exchange level Identification for one TP.

Vendor Invoice creation through EDI (Transaction MIRO)

Dear All,
We want to implement Vendor Invoice creation thro EDI .(Transaction
MIRO)
We are not finding any suitable EDI Function Module in SAP which
would take care of more than 20 items and run a MIRO or any
equivalent transaction .
Can any one please advise if any Function module exists ? We need it for
Invoice creation with GR reference as well as without GR reference .
Thanks
Sanjay.

Thanks Naren,
I will come back after checking the fn module.
- Sanjay

Handling multiple EDI transaction

Hi,
We are getting multiple EDI transactions (940, 850 etc) from our customer. I have defined one Sender Agreement with service interface as functional acknowledgment and one each for EDI transactions (with service interface 940 and service interface 850 etc) in the same configuration scenario.
There wil be only one communication channel to receive all the EDI files. My problem is whenever I send the EDI 850 transaction it is taking the service interface of 940. Because of that it is executing the 940 interface map instead of 850!!!
Am I doing any wrong in my configuration? When I test the data in test tab of configuration scenario, it is taking the correct service interface, but it is not happening in the run time... I cleared the cache also.. still no luck...
Can someone please help me in this? Please guide me if I am doing any wrong.
Regards,
Vas

Hi,
I assume that you are using Seeburger for EDI data handlings..if yes
sender interface details for the payload (850,940) will be determined from the seeburger workbench configurations ..
after bic mapping execution it will result in two doucments one with FunctionalAck and other with attachement(payload..can be 850 or 940) based on this attachment name will compare with the entries of seeburger workbench and fetches the sender details and based on this receiver will be identified...
Hope this gives you need info..
Regards
Rajesh

EDI transaction code

Can you tell me some important EDI related transaction codes and why they are used?
Also can you brief me about the important EDI examples that are generally used ?
(Links are not necessary, if you can give me good brief idea for the above questions, that's enough for me)
Thanks.
Krishen

my mail id [email protected]
Thanks in advance and please send me the material.
Regards,
Krishen

EDI 824

Hi,
Can anyone send me the flow or steps for EDI 824 transaction document....
Thanks,
Priya

Mirza,
Can you tell me how you were able to configure check management and then also create EDI 820 and 831 files? I can get one or the other, but not both using classic payment medium programs RFFOUS_C and RFFOEDI1.
We want to execute check issuance for payments but transmit via EDI to our bank for check printing and distribution.
Thanks

EDI validation Error: Segment GS(Functional Group Header) at guideline

Hi,
I am working on EDI 272 transaction(inbound).
I created ECS file for EDI 272 and validated the EDI 272 data with ECS file in the B2B document editor. Validation was sucess in the B2B document editor
when I upload the same ECS file and tested the same in B2B. I am using EDI version 4020.
I am getting the following error,
Segment GS(Functional Group Header) at guideline position 0200 is missing. This segment's standard option is Mandatory.{br}{br}This segment was expected after:{br}{tab}Segment Count: 1{br}{tab}Character: 105

Hi Anuj,
I created new ECS file without Envelope.
Now I am getting the following exception
<errorCode>AIP-51505</errorCode>
<errorText>5020: An invalid character was encountered in a data element.</errorText>
<errorDescription>
<![CDATA[Machine Info: (dgia21a.cccis.com)
Element ISA11 data type must be 'Alphanumeric'. Segment ISA is defined in the guideline at position 010.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Position: 11 {br}{tab}Characters: 82 through 83 ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
<errorDetails>
<parameter name="InterchangeControlStandard_RepeatingSeparator" value=""/>
<parameter name="InterchangeTrailerControlNumber" value="000000001"/>
<parameter name="InterchangeChildCount" value="1"/>
<parameter name="InterchangeTime" value="1417"/>
<parameter name="InterchangeUsageIndicator" value="T"/>
<parameter name="ErrorScope" value="Interchange"/>
<parameter name="SubelementDelimiter" value=""/>
<parameter name="RepeatingSeparator" value=""/>
<parameter name="InterchangeSecurityInfo" value=" "/>
<parameter name="InterchangeReceiverQual" value="ZZ"/>
<parameter name="DecimalSeparator" value=""/>
<parameter name="InterchangeAuthorizationInfoQual" value="00"/>
<parameter name="ElementDelimiter" value=""/>
<parameter name="InterchangeComponentElementSep" value=""/>
<parameter name="InterchangeControlVersion" value="00402"/>
<parameter name="InterchangeAckRequested" value="0"/>
<parameter name="InterchangeSenderQual" value="ZZ"/>
<parameter name="InterchangeReceiverID" value="BBBBBBBBBBBB"/>
<parameter name="ReleaseCharacter" value=""/>
<parameter name="InterchangeDate" value="001212"/>
<parameter name="SegmentDelimiter" value=""/>
<parameter name="InterchangeControlNumber" value="000000001"/>
<parameter name="InterchangeAuthorizationInfo" value=" "/>
<parameter name="InterchangeSenderID" value="AAAAAAAAAAAA"/>
<parameter name="InterchangeSecurityInfoQual" value="00"/>
</errorDetails>
</Exception>

EDI : How To Start.

hi gurus,
can anybody tell me how to start working with EDI. Detail Steps for EDI. Transaction Code for EDI.
i dont know anything about EDI. Please Help me.
if possible please send me any practical Example regarding to EDI.
points will be definately rewarded.
thanks
Vinod

Hi,
EDI
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
http://www.erpgenie.com/sapedi/index.htm
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents (IDOCS).
EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.
EDI is also called paperless exchange.
Advantages:
Reduced Data entry errors
Reduced processing time
Availabilty of data in electonic form
Reduced paperwork
Reduced Cost
Reduced inventories and better planning
Standard means of communications
Better business process
EDI has two process
1. Outbound process
2. Inbound process
OP:
1.Application document is created.
2.IDOC is generated
3.IDoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.Edi document is transmitted to the business partner
6.The Edi Subsystem report status to SAP
IP:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
regards,
vineela.

EDI Gateway Setup

Hi All
I need info regarding EDI Gateways(EDI Outbound Transaction setup)
I am trying to generate the falt file for Outbound Purchase Order using standard Extract programs. But I am getting empty file.
I have gone through some documents available on Net. But I could not fix this problem.
I wanted to know the basic steps we need to perform to get the output file.
I am using standard catagories only so far. I Defined values for some Categories and attached those categories to some of the columns in the Interface Table.
But still I am not getting the output file.
Do you I need to delete the columns from Output Definition to which I have not attached any category.
When I setup Trading Partner Information, Just I created A dummy name for the parnet header and attached one of the supplier name and supplier site to that partner. Will it validate the partner information somewhere while extracting the data. Is this partner information need to be present somewhere or we can create the dummy names for the testing purpose.
Please feel free to send info to [email protected]
I appreaciate your help regarding this.

If you are looking at e-Commerce Gateway, you should also look at the full Oracle B2B solution, which includes complete integration, EDI, mapping, TPM, AS2 etc. capabilities. It provides a standards-driven, flexible, end-to-end solution that you won't find elsewhere. If you are and e-Business Suite user, this would be an ideal choice.
John Morris

EDI 943 Corresponding IDOC

Hi,
Can anybody worked on EDI 943 Transaction set. What is the IDOC used to post the EDI 943 data.
Thanks & Regards
Vijayanand Poreddy

I want an idoc to send Warehouse Stock Transfer Shipment Advice data.
Regards
Vijayanand Poreddy

EDI 997 flow

Hi,
I am working on EDI transaction. We recieve EDI 101 transaction and send EDI 997 functional Ack.
I configured B2B to handle EDI 997 ack. I set Document Protocol Parameters in host side (ProcessBA_997 - 1.0) - Initiator and client partner side (ProcessBA_997 - 1.0) - Responder. B2B is able to send 997 transaction to configured transport protocol.
The issue is that B2B is taking the Document Protocol Parameters values (to generate ack) from Host side and not a client partner side parameters. This parameters will vary for client parnters.
Kindy advise me how to override the host side document protocol parameters. Thanks in advance.

If you want a custom FA as per the trading partner then better approach will be inserting the FA from backend.
Receive the message B2B to backend then change as per your requirement and insert FA again to B2B.
Rgds,
Nitesh Jain

EDI type to create invoice

Hi,
Pls advise me which EDI message type is used to create INVOICE.
Regards,
Student

Hi,
The EDI 820 transaction is used for Payment Order/Remittance Advice. What this transaction does is it be an order to a financial institution to make a payment to a payee. Hence it uses the basic idoc type GSVERF01: Idoc input credit memo procedure. Im not sure DELCON is the message type used for this basic idoc type. You can check the basic idoc types assigned to a message type in T.code WE82.
Hope this gives some insight into your requirements.
Thanks,
Kumar.

EDI 831 transaction

Similar Messages

Maybe you are looking for