EDI 894 transmission

Hello Gurus,
I want to know the basic idoc type and the message type used for EDI 894 transmission. Can someone send me the list of EDI transmissions and the SAP basic idoc type and message type recommended to be used for these transmissions???
Thanks in advance

Hi,
Please use message type FINSTA and IDoc type FINSTA01.
Regards,
Ferry Lianto

Similar Messages

EDI 821 transmission - URGENT

Hi Gurus,
I am struggling to find the Basic IDoc type, message and process code used for EDI 821 (Income Asset Offset) Outbount Transaction.
Please respond if anyone knows about it.
Thanks in advance.

Hi,
Please use message type FINSTA and IDoc type FINSTA01.
Regards,
Ferry Lianto

Urgent - Idoc type and the Message type

Hello
Its very urgent. I want to know the basic idoc type and the message type used for EDI 894 transmission (Delivery / Return Base Record). Please respond at the earliest.
Thanks in advance

HI
Pratibha
How are you ?
Please check the below links:
http://scn.sap.com/thread/990524
http://www.erpgreat.com/pm003.htm
http://scn.sap.com/thread/1386811
http://scn.sap.com/thread/1078741http://www.erpgreat.com/plant/what-is-equipment-master.htm
http://benxbrain.com/en/index.do?onInputProcessing%28brai_object_thread%29&001_threadid=0000835100&001_boardtype=01&sysid=PI1&pgmid=R3TR&object=TABL&obj_name=EQBS&child_param=
Mutti

Please share your understanding and experiences on Picking Request Output.

Hi,
Have you ever involved in any project which related to the 'Picking Request' Output IDOC.
Normally it is triggered from Delivery output and corresponding picking data will be sent...
Please share your understanding on how to trigger this kind of Picking request ouput from delivery processing.
For example, you are the person is assigned to explore an existing SAP-system. Your task is to simulate an order cycle and most important points is to trigger the 'Picking request' Output IDOC in delivery order. But you dont know what Sales order type,Dlv type is used. The only thing you knew is the picking request output type is ZXXX from delivery header output.
How do you find out corresponding sales order type/Dlv order type/Billing order type according to an output type name ZXXX.
First, i will share my ideas:
Through ZXXX we could get corresponding condition records, as there contain some info like dlv type/sales order type..kinds of combinations..Follow that, i will find already proceessed sales documents. Then refer those document to do the re-creation.
Please kindly let me know your ideas.
Thanks!

Hi there,
Define a new O/p type. Select EDI in Transmission in Default values of O/p type for external system. Select ALE for internal system.
Assign an access sequence to that.
Maintain the determiantion procedure. In the requirement routine, put a condition that it should trigger only after picking / packing is done.
Assign the O/p to the delivery type.
In WE20, define a new partner to whom you want to send the IDOC. Give the required details.
Define a new IDOC processing prog & assign that to the process code of the IDOC in the partner profiles.
So whenever you do picking, the Op type will be trigered which will be processed by the IDOC prog & send it to the external system.
Regards,
Sivanand

Modify ACH file format in F110

Hi everyone
I have to modify the ACH file format using PMW
How do i proceed?
Do I copy the function module FI_PAYMEDIUM_ACH_30 and add the necessary codes
then assign it to event 30 in FBZP or there is a BTE to enhance the event modules?
thanks a lot for your help

Prema,
Yes, you should copy the standard function modules;
add your coding;
replace the standard FM with your own in the relevant nodes.
However, if your bank has capability of accepting EDI (Idocs) transmission, then go that route. I found this way much better and flexible. Although you end up having lot of Idocs.
regards,
Vishal.
Edited by: Vishal Thakur on May 25, 2011 1:02 PM

EDI Transmission Issue!! Interface issue

Dear Experts,
I've been trying to connect with Client system for a couple of weeks now to debug and iron-out a possible issue we uncovered in our parallel EDI transmissions from our SAP system back on April 29th and 30th. The EDI Transmission is not happening. We're not able to establish the interface with the Warehouse Managment System. Please suggest some solutions.
Thanks in advance.

Hi,
What systems are you trying to connect. ECC with SAP WMS(Decentral)?.....In this case you will have to look at the Distribution model between the systems. Are you using any Middleware?
Thanks
Vinod.

Checking EDI Transmission Status (850 PO Outbound)

Hi,
We have implemented the 850 outbound PO EDI transaction for our customer. We would like to explore the following options for further tracking of the EDI sent to the factory.
Background:
EDI extract is generated in Oracle Apps using 850 outbound transaction (PO). This EDI extract is sent to our supplier/factory where it is converted into a Sales Order. The EDI is transmitted to the factory using FTP mechanism.
Requirement:
We would like to know if there is any way in which the factory can send back a response to say Oracle Apps, that confirms that the EDI extract has reached it correctly. This is to ensure smoother transmission of the EDI to the factory.
If there has been a similar scenario, then please share your views/thoughts on this.
Thanks,
Nitin Jain

Hi
yes, we have Rosettanet Standard which fulfills your requirement.
You need to implement Rosettanet Standard using any Integration Tol (webMethods is best suited for Rosettanet).
I have been in a project of same kind, we developed for POO and POCO in the same way. Once the TP gets the data, and he will confirm us saying that whether he will manufacture or not....
Plz surf this website www.rosettanet.org

Restrict EDI Transmission to the Vendor.

Hello Experts,
I have a question,
Can we restrict the PO changes being transmitted to the Vendor even though its setup as an EDI Vendor.
Scenario.
1. PO Gets Created.Its gets transmitted to the vendor through EDI.
2. Now the user changes somethng in the PO and changes are Transmitted again.
3. But if incase of my client there are numerous times changes are done and not always you want to send the ORDCHG Idoc to vendor.
Question:
1. Is there a functionality avialable to restrict the EDI from being transmitted to vendor even though its an EDI Vendor.
2. I know we can create a mapping of saying change only if certain key fields are changed but they wnt to generate the Idoc but restrict sending sometimes.
Means they can send those changes sometimes but sometimes not send.
Thanks,

HI,
1. once you have finished the mapping details with your external partner you have to send a "initial load" all masterdata needed for this vendor.
2. after that you can use the change pointer solution to send changes of an item to the externam partner.
how to do that:
1. you have to create a logical system (Tcode: SALE) for your external partner or converter system
2. maintain your IDoc Settings in the partnerprofiles (Tcode: WE20)
3. customize your distribution modell (Tcode: BD64)
4. customize ports / RFC Destinations as well (WE21 / SM59)
5. send Masterdata with Tcode: BD10
for the change pointers look at tcode:
1. SCDO.
2. activate CP at BD50
3. define CP at BD52.
4. send changed Masterdata: BD21
Regards,
Gordon

EDI seeburger interface

Dear experts,
i have a inbound scenario EDI -> XI -> R3
1. I am thinking of going the BIC mapping way like creating a BIC mappign installing in XI and specifing the mapping name in the module section of the sender file adapter as specified in this blog /people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
2. however when i check in the communication channel and try to select the adapter, i can also see a Seeburger AS2 adapter...
so i am confused ...which option is correct ....
option 1 : to use BIC mapping and mapping name in module section of the sender FILE adpter or
option 2 : to use sender SEEBURGER AS2 adapter..
advance thanks

>
Ravi Mehta wrote:
> Dear experts,
>
> i have a inbound scenario EDI -> XI -> R3
>
> 1. I am thinking of going the BIC mapping way like creating a BIC mappign installing in XI and specifing the mapping name in the module section of the sender file adapter as specified in this blog /people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
>
> 2. however when i check in the communication channel and try to select the adapter, i can also see a Seeburger AS2 adapter...
>
> so i am confused ...which option is correct ....
> option 1 : to use BIC mapping and mapping name in module section of the sender FILE adpter or
> option 2 : to use sender SEEBURGER AS2 adapter..
>
> advance thanks
Note that you will use the Seeburger AS2 adapter only if your transport protocol is AS2.
In case you are just accessing files from a FTP then you dont have to go for the AS2 adapter.
The BIC modules can be attached any where.. it has nothing to with the transmission protocol.
So the choice of the adapter is based on how the transmission protocol is needed.

Purchase order distrubution using EDI

Hi, SAP gurus!
I am trying to set up Purchase order distrubution using EDI. ORDERS idocs will be sent through middleware message broker. I added ORDERS idoc in LS partner profile outbound data and set up medium type 6 for PO output. Something else is missing since I can't add manually output to a purchase order - error message VN032: "Maintain outgoing EDI-connection data for partner"
"Short Text
Maintain outgoing EDI-connection data for partner &
Diagnosis
The system could not locate the EDI partner agreements (outbound) for partner .
System Response
You cannot use transmission medium 'EDI' with this partner.
Procedure
Maintain the EDI partner agreements for partner . Make sure to create entries for output control as well as for outbound parameters."
What else is needed besides outbound idoc data in partner profiles?
Maybe I have to do everything completely different?
Thanks!

If it's an EDI interface, you should be using a trading partner partner profile type (KU or LF) ... a customer or vendor ... not a logical system, although you can use LS it's not really an optimal solution and you need to create more generic configuration to generate your IDocs from your business documents.
I cover configuration of output control for outbound EDI invoices in a series of blog postings at:
http://it.toolbox.com/blogs/ehadzipetros/dazed-and-confused-output-control-ate-my-brain-33944
http://it.toolbox.com/blogs/ehadzipetros/no-longer-dazed-and-confused-my-brain-finally-ate-output-control-34065
http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-a-contented-glow-34232 and
http://it.toolbox.com/blogs/ehadzipetros/my-brain-on-output-control-bringing-it-all-together-34416
I also cover it extensively in my new book from SAP Press "Architecting EDI with SAP IDocs". All steps are covered in the blog postings and the book.
Good luck.

EDI billing outputs are capturing credit memos as well as invoices

I am a newcomer to the company I am currently with, and to this forum, and I have 6 years of experience in EDI and SAP SD.
I am working on a project to determine why our EDI billing outputs are capturing credit memos as well as invoices, and attempting to send them by EDI, causing failures in our Seeburger translator. Most customers donu2019t want credit memos by EDI. My goal is to track backwards and determine what portion of the EDI process in SAP is pulling credit memos rather than just invoices. I suspect that someone intentionally made changes in the past to put this in place, but we need to have a message type that includes invoices and credit memos, to be attached to specific partners that want this, and another more standard message type that sends only invoices.
The message control for the example partner specifies Message Type ZURH (customized by this company for some reason), Application V3 (which seems standard), and process code SD09 (which seems standard). Could someone help me to navigate to an area where I may be able to find out what parameters are used to determine what transaction types are pulled to be sent out by EDI for billing? I suspect that the issue may be in Application V3, but I am unable to find any help to view u2018Applicationsu2019, because application is such a widely used word.
How can I display/change Application V3, in order to check itu2019s contents?
Any other ideas why credit memos may be included would be appreciated, and I always appreciate having the transaction codes mentioned as well.
Thank you in advance for your assistance.
Application V3 (what specifies what transaction type this pulls?)
Message Type ZURH,
Process Code SD09.
Access Sequence used is ZSD1 Billing Documents (Access Sequence ZSD1 does not appear in transaction V/48 (?))
Transmission Medium is 6 EDI.
The program is RSNASTED, and the FORM Routine is EDI_PROCESSING.

Satish,
Thanks for the suggestions.
I checked transaction VV33 u201CDisplay Output Condition Records: Billingu201D for Output Type ZURH, Key Combination Sales Org/Payer, and I find the example customer linked to ZURH, as I would expect (5010013645     BEST BUY CANADA Vendor #41448     PY          6     1).
I donu2019t see any data about specific transaction types such as credit memos or invoices, so I may not be looking in the right place. I donu2019t find entries under any other key combination. How would I check if Output Condition records are maintained for credit memos?
In regards to the output type being assigned to the credit memo billing type (ZG2U), Iu2019m afraid I donu2019t know how to check that either.
In NACE, I see that u2018Proceduresu2019 list the CTyp (?), and procedure US0001 is the only one that includes credits and debits. I donu2019t recognize the Ctyps ZDN0 and ZCN0. The billing type is ZG2U, which I don't see in any of the Procedures:
10     1     RD00     Invoice
20     2     ZPRO     Proforma Invoice
30     1     ZCAN     Canadian Cust. Inv
40     1     ZCOM     Commercial Invoice
50     1     ZDN0     Debit Note
60     1     ZCN0     Credit Note
How would I be able tell which u2018Procedureu2019 is being used for Application V3, and how would I change that to another Procedure for testing?

EDI management for POs

I just am looking for a simple outline (with possible screenshots) regarding managing and following up with vendors that are set up with EDI. All the vendor master data and materials master data is set up, I am just looking for a basic outline for EDI PO processing and managing/overseeing the IDOC messages (both inbound and outbound) and the possible responses to vendor's IDOC messages.
Thanks.

Hi,
Managing/overseeing IDOC Messages:
Transactions : WE02 or WE05 (Display IDOC)
EDI PO Processing:
Define the output type NEU (new) or your own output type for XXX in purchasing master data and assign the Message Control dispatch time 4 (immediately with application update) and the transmission medium EDI. Choose the output mode Transfer IDoc immediately and Start subsystem immediately for XXX in the partner profiles of the IDoc interface and assign the logical message ORDERS to the combination Application: Purchasing orders, Output type: NEU (new). IDoc type ORDERS01 is assigned to this logical message.
Define Partner Profiles for your Partner. Maintain Application and Output Type to an IDOC Type in Partner Profile under additional outbound parameters.
1. Message determination: Call the master data from the application and create the message as a message- or condition record, that is to say, you define the conditions under which the message is found and proposed, as well as the message properties. For example, you can enter the purchasing organization and the business partner as the conditions and the output medium (in this case 6 for EDI), dispatch time and language in which the message is to be sent as the output properties.
2. Message processing through IDoc dispatch: The messages are sent by the Message Control module as defined in the condition record, especially with regard to the selected dispatch time. You must also define a dispatch time (output mode) in the partner profiles of the IDoc interface: standard combinations of the two times are shown in the table below. The Message Control parameters from the partner profiles must also match the corresponding fields in the output type. These parameters include:
− Application
− Partner
− Partner function
− Output type
The central selection program of the Message Control module, RSNAST00, locates and triggers the form routine EDI_PROCESSING in the program RSNASTED in table TNAPR for the selected output type. EDI_PROCESSING reads the partner profiles and uses the process code to determine the function module which is to generate the IDoc. The process code also determines the type of further processing, for example whether the IDocs are to be processed by the ALE service.
The function modules for generating the IDocs are usually called IDOC_OUTPUT_<MT>, where <MT> represents the relevant message type. Depending on the output mode, the generated IDocs are either collected or forwarded for immediate dispatch. If the IDocs are collected, the report RSEOUT00 must be scheduled in order to forward the IDocs for dispatch.
Regards,
Naveen.

EDI: Field REFINT in control record

I am trying to send orders.orders05 idoc from ecc to xi
the message that I get in we02 in ECC is
EDI: Field REFINT in control record with value 'T080902134731A ' is invalid
Does somebody knows where this field is configured ?
when I edited this idoc in we02 and erased this value the process was sucessfuly
but when I try using we19 it assigns this value automatically
thx
Shai

hi
it depends on use
As a reference, this field contains the number of the interchange file, as entered in the EDI standards.
An interchange file can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.
cheers

PI EDI help: What is the source of ISA13 in a IDOC to EDI mapping

Hello Experts,
It would be of great help if you can provide the field mapping for ISA 13 in outbound from IDOC sceanrio:
IDOC: INVOIC02 - to - EDI 810 mapping.
Is it the best practice to have ECC send the value in a particular IDOC field ( like RFINT) or PI has to use a custom function to populate the ISA13 field.?
Thank you,
Patrick.

Hi,
ISA13 is for Interchange Control Number. It is a control number assigned by the interchange sender.
Normally its Sequential number starting with 000000001 and incremented by 1 for each subsequent ISA between sender and receiver.
This is a very useful value to include. It creates an explicit link between the IDoc and the EDI transmission. This number eases Production Support greatly. When there's an issue with a Partner EDI transmission, the Partner's EDI support people want to know the Interchange Control Number
The IDoc interface does not process or check this field.
regards
Ganga

Comparison between split Adapter in Seeburger and EDI Separator

Hello All,
Currently we are designing EDI interfaces using B2B Add-On.
I am trying to compare the split Adapter of Seeburger and EDI Separator of B2B Add-on.
In Seeburger Splitter configuration:
The additional split configuration helps to map the Sender ID, (EDIType,Transaction,Version) combination to split channel and sender agreement.
I believe a List of Sender Id, Mappings (Standard, Transaction, Version) combinations can be added to the same Split channel and Sender Agreements.
In B2B Add-On:
The sender ids , EDI details are directly mentioned in the channel and it is bound to sender agreement.
Does it reduce the flexibility in EDI Scenarios.Is that a correct point of view?
Your inputs highly appreciated.
Thanks.
Regards,
Sudharshan N A

Dear Sudharshan,
yes, I would say that this is a correct point/observation. When the Seeburger Adapters were introduced many years ago, one focus was put on the flexibility by keeping all functionality related to the "format conversion" (Classifier/Bic/Splitter) completely separated from the "data transmission" functionality directly in the channel.
This way, the format conversion modules could be included in any adapter that was running on the AdapterEngine and not just to the See-Adapters.
In a typical setup on client side, almost all inbound channels were using the "AUTO" functionality to detect all required parameters to select the right Split-Channel...so all channels had the same module-chains included (no matter if it was an AS2-Channel or a simple FILE/FTP-channel.
This also allowed for easy reprocessing of any received file (via AS2, X400 , OFTP or else....) by just putting the file again to a file-channel with the same module-chain parameters.
Kind Regards
Stefan
Btw... I am not very familiar with the B2B AddOn, but if you have additional questions regarding the Seeburger-EDI-Adapters, feel free to ask...

EDI 894 transmission

Similar Messages

Maybe you are looking for