PO confirmation through EDI

Hi folks!!
I have send a PO through EDI to my supplier, which he has received and send an order acknowledgement, but it is not updated in the PO. While the inbound parameters are also maintained.
What could be the possible missing assignments or objects, a detailed reply is requested.
Best regards,

Steps to configuration
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
Use Tcode: SALE
u2022 Create a Customer Distribution Model (CDM);
u2022 Add appropriate message types and filters to the CDM;
u2022 Generate outbound partner profiles;
u2022 Distribute the CDM to the receiving systems; and
u2022 Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Regards,
Amol

Similar Messages

Order confirmation through EDI

Hi,
I need to confirm a sale order by triggering an output type when a sale order is created by an inbound order.
The output type i created triggers if i create a sale order manually but its not working when a sale order is automatically created from a inbound order.
Kindly help me.

Have you checked the authorisation of the user that is used when the Sales Order is created automatically.
Thanks

Vendor Confirmation via EDI

Hi
I am analising different possibilities to implement vendor confirmation via EDI?
Which Idoc - message type is suitable for Shipping Notification from vednor?
Is Inbound delivery created after Shipp. Notif comes to ERP?
What might be scenarios related to Purchase Order Confirmations.
ERP part only is my interest.
Thanks for hints
Mariusz

You can use Idoc message type DESADV to get confirmations from vendor.As soon as you get vendor confirmations through EDI system coverts to into inbound delivery.
If you are looking inbound delivery then you can use vendor confirmations.
Edited by: Sridhar Jayavarapu on Feb 24, 2011 5:32 PM

PO Revisions through EDI

Hi All,
We used to send POs to some other Application through EDI. One of the POs has not interfaced to the third party Application through EDI. We have checked all the trading partner and supplier setups. The only issue we have found is that the PO has been revised as it has Printed_Date and print_count is present in PO_HEADERS_ALL.
So pls suggest how can we push PO revisions through EDI.
Version - 11.5.10.2
Thanks!!!!

Hi,
If you wish to receive vendor confirmations via EDI, the IDoc interface must have been installed
When an order acknowledgment is received via EDI, the system checks whether just the acknowledgment number is to be recorded, or also quantities and dates.
Refer the attached link for more information on customization settings;
http://help.sap.com/saphelp_46c/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
If you work exclusively with order acknowledgments, only the acknowledgment number is recorded on the item detail screen. (In this case, no confirmation control key exists.)
If you work with several confirmation categories and therefore a confirmation control key exists in the PO or scheduling agreement item, the quantities and dates shown in the order acknowledgment are recorded by the system.
If you want to take a look at acknowledgments that have been received, choose Item ® Confirmations ® Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI.
Br,
Tushar

Unloading point not transmited to vendor through EDI in Scheduleing Agreeme

Hi ,
Unloaloading point details are not transmited to vendor through EDI in scheduleing agreement . What would be the possible reason ? . Auto unloading point detials are their for perticular material in message details .
RB

Hi ,
Currently we are using Message Type - GSVERF , Basic type - GSVERF03 , Processing code- GSVE , FM-IDOC_INPUT_GSVERF_START and assigned this FM to Object Type- BUS2094)..which is giving above error. I just found that process code GSVE is for Outbound message
Can any one suggest / confirm what should be exact Message Type , Basis Type, Process code and Funct. Module requiered for processing EDI inbound message in MM - Logistics Inv Varification ?
Thanks
NAP

Re : Inter company stock transfer through EDI

Hi
      How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
How to do this.
Thanks
Anto

Hi,
continues from here,
Inbound file:     edi_in
Function module:     See text below.
Status file parameters
Directory:     /home/edi/<portname>/
Outbound file:     status.idoc
Function module:     Leave blank if using above
u2022     Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
     Portname (upper case):
                         <portname>
     Exchange directory name (lower case):
                         /home/edi/<portname>
     where <portname> consists of:
     EDI<system name><client number><id char>
     <system name> is the name of system on which port exists eg.      F01, PG1 etc.;
     <client number> is name of client on system which will use this      port; and
     <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc.      typically,      u2018au2019 will denote dynamic outbound file naming (used      for testing) whereas      u2018bu2019 will denote static outbound file naming.      All ports will use static      inbound filenames.
For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A. The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D can be used in the u201CFunction moduleu201D field of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
2.4.2.     Control of EDI processes in R/3
2.4.2.1.      Maintain: Outbound Process Code (WE41)
IMGCross-Application ComponentsALE Extensions  Outbound
Check that the outbound EDI processes in the R/3 system are defined. Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
The following assignments are available for R/3:
2.4.2.2.      Maintain: Inbound Process Code (WE42)
IMGCross-Application Components  ALE  Extensions  Inbound
Check that the inbound EDI processes in the R/3 system are defined. Indicates what kind of inbound processing to execute.
     A long list of options is available under Processing by function module, relevant ones are:
INVF     INVOIC FI     Invoice receipt (Financial Accounting)
INVM     INVOIC MM     Invoice verification (Mat Management)
ORDC     ORDCHG     Change customer order
ORDE     ORDERS     Create customer order
ORDR     ORDRSP     Purchase order confirmation
2.4.2.3.      Control: System Process Codes (WE40)
     Choose Processing by task. Check that the codes indicating the type of EDI processing error are defined. The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
2.4.2.4.      Control: Status maintenance (WE47)
     Check that the codes indicating status of IDoc processing are defined. The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50. These values are delivered by SAP and cannot be customised.
2.4.2.5.      Control: Partner Types (WE44)
     Check that the codes that identify the commercial relationships between the receiver and sender are defined. Values are delivered by SAP. Names of the programs and routines that validates the entry of the EDI trading partner ID:
Partner type     Report name     Form routine
B - Bank     RFETESTP     READ_T012
KU - customer     RSETESTP     READ_KNA1
LI - vendors     RSETESTP     READ_LFA1
LS - logical system ( ALE)     RSETESTP     LOGSYS
2.4.2.6.      Control: Forward Inbound (WE45)
Allows for the forwarding of IDocs to a specific application. Contains the exactly defined destination of an inbound IDoc within the SAP system. Usually no changes are required.
2.4.2.7.      Control: Status Process code (WE56)
Choose Processing by task: The following set-up has been provided as default:
Process code:     EDIS
Identification:     TS30000078
Description:     EDI-IDoc status record processing
The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
3.     MM IMG CONFIGURATION
3.1.     Global settings (IMG):
3.1.1.     Units of measure (IMG  Global settings):
The ISO code is important for EDI. It is used to convert the internal SAP units of measure into standard units.
The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
3.2.     Link Schema to Purchase order
Check the following:
IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
Select transaction: Assign Schema to purchase order
Add:      Usage =B for output
     Application = EF for purchase order
     Procedure = RMBEF1 for purchase order
3.3.     Link application to EDI interface via message control:
IMG  MM  Purchasing  Messages  Output Control
Check following under Output Control:
     Condition table
     Access sequence
     Message types
     Message schema
     Output control
3.4.     Enabling Multiple Output for Purchase Orders (Optional)
For example: EDI & Printing
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022     Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
u2022     Goto Define message types  maintain message types:
     Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
u2022     Goto Message Schema  define message schema  maintain output determination procedure:
     Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
     - Add a NEU1 record to table TNAPR. The program FORM Routine and layout must be specified. (Copy an existing NEU record). (Transaction OMTB)
u2022     Goto Processing program  Define Processing program  Output by partner type.
     - Add NEU1 record for VN (vendor). (Transaction OMTG)
3.5.     Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
     - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
u2022     Goto Processing program  Define Processing program  Output by partner type.
     - Add NEU record for VN (vendor). (Transaction OMTG)
4.     SD APPLICATION REQUIREMENTS
Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
Reference SAP Course manual Chapter 11.
4.1.     EDI Configurations
4.1.1.     Conversion of SAP item categories to IDOC item categories (VOE1)
IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
Add the following entry:
For Standard Item description :     0     OR     LDN
Typically error message: ''Transaction LDN is not defined".
4.1.2.     Partner functions
IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
Check that the following partner functions exist: (at least)
SP     Sold-to party
VN     Vendor
BP     Bill-to party
SH     Ship-to party
Note - the German abbreviation is passed to the IDoc.
4.2.     S&D Sales Configurations
4.2.1.     Maintain Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
Add LDN for standard item:
          Item type = B
          Relev for billing = B
          Tick following:     Bus data item
                              Sched line allowed
                              Credit active
                              Pricing
          Screen seq. grp = N
4.2.2.     Assign Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
Add/Update the following entries:
     1     2     3
Sales doc type     OR     OR     OR
Item category group     NORM     DIEN     LEIS
Item category     LDN     TAD
LDN     LDN
4.2.3.     Assign Schedule line categories
IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
Add Item category LDN to table (with no other parameters).
4.3.     S&D Pricing Configurations
4.3.1.     EDI pricing condition types
IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
Maintain the following condition types:
     EDI 1 - Calculate type =C for Quantity
     EDI 2 - Calculate type = B for Fixed amount
4.3.2.     SD Pricing procedures (V/08)
IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
Maintain pricing procedure for ZVAA01 (Standard).
Select control and add EDI1 and EDI2 as steps 1 and 5 respectively with no other parameters.
5.     INVOICE IMG CONFIGURATION
No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
Thanks,
Swamy H P

Creation of Sales orders through EDI

Hello,
We have a problem when creating sales orders through EDI.
We are getting IDOCs with a delay of 1 second.Before
creating sales orders through the posting function
module IDOC_INPUT_ORDERS, we need to validate for
reference Purchase order number in the IDOC. If there is
any sales order in the database with the Purchase order
number in the current IDOC that sales order should be
blocked.
We already put a validation in the User-Exit of the
posting function module. Because of the frequency of
IDOCs we receive, this validation is getting failed.
Can anybody tell me, how to process only 1 IDOC at any
given point of time before the Posting process.
Thanks,
Madhusudan.

Hi Sanjeev,
Thank you very much for helping me out in this problem.Still I haven't got the solution.
I tested the above mentioned configuration option by putting the Check Purchase Order Number field to 'A' in the transaction VOV8. But while creating sales orders, it is giving only information message. Is there any other way, to restrict the Duplicate PO value through configuration setup.
can you also explain how to use Enqueue and Dequeue FMs in the inbound posting function module.
Regards,
Madhusudan.
Message was edited by: Madhusudan Budati
Message was edited by: Madhusudan Budati

Creation of Sales Order through EDI

Hi
Can anybody explain in detail the configuration steps involved in creating the sales order through EDI. If possible with screen shots.
Points will be rewarded.
Thanking you
chan

Hi Hari & Siva,
Could you please send the document to my mail id
[email protected]
Thanks in advance
MMVD

Goods Supplier details through EDI - Purchase Order

Hi All,
We are sending purchase orders to vendor through EDI. Generally we do not have details of the Partner - Goods Supplier (GS) in the idoc in the segment E1EDKA1. .
Now our client wants to show the details of GS also in the segment of the idoc. As per SAP note 456127 , SAP has not given provision for it.
Has anyone got this type of requirement , and has someone any idea on adding a new segment showing Goods Supplier in it.
Thanks in advance.
Regards,
Vengal Rao.

Hi,
Please check the below links...
http://help.sap.com/saphelp_sm40/helpdata/en/af/5f28a7669648dfb71b418d243f2a82/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/content.htm
Hope it may helps you.
Kuber

Remittance Advice to Vendor through EDI, message REMADV

Hi Guru
I want to send a remittance advice to vendor only through EDI after running payment run. But standard SAP requires configuration for Vendor and as well as House Bank and generates two Idocs one for bank(Message type PAYEXT-PEXR2002) and one for Vendor(Message type REMADV-PEXR2002).
The requirement is only to send the remittance advice to vendor but not to the bank is any way that i can stop generating idoc to bank.
THANKS & REGARDS
Pavan
Edited by: Pavanks on Sep 14, 2009 10:28 AM
Edited by: Pavanks on Sep 14, 2009 10:29 AM

hi Pavan,
you want to do the open item clearing without the banking file throught auto payment run, do you? can you try to use other payment method , like check.
thansk

Check Payment advice through EDI

Hi,
I need a solution to send the payment advice to bank through EDI.
For that i created partner profiles for vendor and bank. I activated EDI in vendor master also.
And i attached EDI accompaying sheet also to the FBZP t code.
for this we created a new payment method and testing. it is working.
our client is asking: He want to send the payment advice for the payment method 'C' - Check to his bank through EDI. What we have to do for this.
For this if we give C in payment method in F110 we have to use payment method program only not EDI program.
Please guide me
sateesh kumar

Hi Sateesh,
Generally payment advices are directly sent to Vendor, but sometimes clients will sent the payment details and payment advice to the bank.
In your case, if u want to select the Payment Method C, then if u give RFFOEDI1 program for EDI setting, then u cant print your cheques locally.
One Alternative is that use Payment Medium Workbench (PMW) in that check management option is present, try with that.
I am not sure how far it is going to be successful.
Regards
srikanth

How to Send Purchase Order through EDI/IDOC.

Hi Experts,
We are using SAP ECC.5. And intending to send the Purchase Order to Supplier through EDI/IDOC and Receive the Inbound Acknowledgement.
Appreciate, if you could help me, the required Configuration details for outbound and inbound (PO & Acknowledgement).
Reg
Kumar

Hi Kiran
Many thanks for the response. It is true that by changing the message type to EDI can generate idoc. What is not clear is any other config we need to do interms of Message generation, Resubmitting failed IDOC etc..
Out requirement is that we would generate the IDOC for New and changed docs and send to external EDI converter.
Inbound, receive the IDoc and post the acknowledgement.
Appreciate, if you could forward any document link which can explain the details.
Reg
Kumar

Create Purchase Order through EDI

Hello Everybody,
I want to know how to create Purchase order through EDI. I will receive text file from third party system. I have made most of the configuration related to EDI like Port -File, Partner Function etc. I am using message type PORDCR and Idoc type PORDCR05.
But i do not know how the SAP first will convert the text file into IDoc and then create Purchase order. Can any body help me how to go about it? What steps i have to follow. I will have text file from that i have to create Purchase order through EDI.
Thanks in advance.
Regards,
Manish

Hi,
Create Purchase Order through EDI
Regarding on your query,
You can use the standard ORDERS05 idoc type itself to send outbound idocs.
It will be the middleware or the integration team that will send this IDOC to the receiving system.
or
Maintain Partner Profile in WE20, RFC Connection to the Middleware in SM59 and Port in WE21.
Maintain Output Procedure/Output Type/Access Sequences/Condition Records from NACE
Generate the Outbound 850 (PO) from ME21N
Regards,
Sekhar

How to skip the Inbound Delivery while updating LA confirmations via EDI

Hi Experts,
I have a requirement wherein I dont want to create Inbound Delivery automatically when updating the LA (or a copied Conf Cat of LA) confirmation via EDI. When we are using the message type DESADV, LA confirmations are being updated, but simultaneously, the Inbound delivery also being created. My client desires that Inbound Delivery should not happen and only LA confirmation should be updated via EDI.
Is there anyway, by which we can skip the Inbound Delivery while updating the LA confirmations in the PO?
Thanks in advance
Regards
Radha Krishna

Hi Prabhaharan,
Thanks for your quick response.
My requirement is to have both AB and LA confirmations. I have included these two in a new the conf control So, your suggestion will not work.
Is there any other way out to fulfill my requirement?
Thanks & Regards
Radha Krishna

While confirmation through COR6N

Hi Expert,
We are working in process order scenario. I have one problem while doing confirmation through COR6N (enter time ticket for process orders) there is one field "CONFIRMATION TEXT" & that field is marked mandatory also and user is filling some text as per business needs like "contractor name" But the main concern is that we don't have any pre-entered list of names of contractors in SAP for which users are regularly making mistakes while typing the names.
and the same field is incorporetd in ZMB51 report through table name "AFRU" field name "LTXA1" but some time user entered wrong name and thus report doesnot reflect correct, how to rectify this issue permanently, is there any option to choose text as a drop down list or like any exit/functional module.
Note:- WE ARE ALREADY USING FIELD REASON FOR VARIANCE FOR SOME OTHER PURPOSE.
With Regards
V. Kaushik
SAP-PP Support Consultant

Hi kaushik,
It is possible to incorporate some more fields in the Time Ticket confirmation for process industries using the T. code OPK1 here you can choose suitability or wage group or other fields in the initial screen of COR6N, And by configuring your selection criteria for the pre-entered list of names of contractors in a field of suitability or wage group. You can make it mandatory using screen variant.
In this way you will be able to drawn Z-reports as well as the standard reports too.
This may be help you.
Regards
Anant

PO confirmation through EDI

Similar Messages

Maybe you are looking for