IDOC Types for Purchase Orders, Vendor Master and Goods Receipt

Hello All,
Can any have idea about the IDOC Types that can be used for triggering when the actions creation/change/deletion on Purchase Orders or Vendor Master or Goods Receipt is performed?
Please let me know the names of IDOC Type, Process Codes, message type... and all the other required information...
Thanks in Advance,
Kumar.

Hello Ferry,
Thanks again for the IDOC Types. I have another question. Can we use those IDOC types for creating/changing/deletion of Purchase orders or Vendor Master or Goods Receipt happens? I mean can we configure in such a way that when ever there is a change or deletion of PO or VM or GR happens?
I have got to know about the IDOC PORDCH01 which can be used for Purchase Order. Can u suggest me which can be used for PO's?
Regards,
Phani.
Message was edited by:
Sivapuram Phani Kumar

Similar Messages

Reg.Output type for purchase order

Dear Sir
I followed your steps but not come to "List of allowed output"
when I select the message for Purchase order(ME21N). There are listing NEU,SPO,MAHN and AUFB.
I just copy the NEU and all,I did not change anything.
Maintain Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Ex:
EF---> TES
Select TES and double click on Mail title and texts and go to
EN- New Purchase Order Print Out,
Select TES again and double click on Processing routines,
Select TES again and double click on Partner Roles
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO(ME21N) and save it. Go to ME22N and print the PO by giving output type TES.
Please help me sir
Rajj

Hi
Go to NACE
Select application as EF Purchase Order
Define TES as out put type there
Vishal...

Custom Exchange Rate Type for Purchase Order

Hi
Our Financial Team doesn't want to change the Exchange Rates on a daily basis, but for place purchase orders with our overseas vendors we need the daily spot rate loaded in the system.
Is there way to configure a different exchange Rate type ? and use this Exchange Rate Type for Purchase Order to use instead of Default type "M"?
Thanks...

Found a soluntion ...
I have coded userexit EXIT_SAPLMEKO_001 component LMEKO001, to fill in Exchange Rate type in the Communication Structure "e_komk-kurst".
Update Exchange Rate Type "ZCUS" under SPRO and updated exchanges in TCURR table for this type. Then, everything else works like a charm.

Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
Thanks,
Veeru.

Hi,
IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
Msg: INVOIC
Basic type: INVOIC02
FM: IDOC_INPUT_INVOIC_FI
Process code: INVF
Thanks,
Kumar

Predefined object type for Purchase order release stratergy

dear experts,
There are already predefined object type for purchase order like bus2012 where i can create new events and methods. I want to know is there any predefined objects for purchase order release strategy. The requirement is there i want to define method, that should display the po release screen. If i bind this method with work flow template, mail should be triggered and if i click the mail po release screen should be opened for respective material...
regards,
Kandhan G

Hello
I'm using the BUS2012 Object type in workflow task but in simulation the task run correct but in the transaction when modify a purchase orden the task send an error...
maybe the error is similar...did you solve this problem?..
Thanks!
Wladimir E.
[email protected]

Class for Purchase order item components and Production order components

I'm looking for a some classes.   I'm very new to objects, so I could be searching for them incorrectly.
The first class I'm looking for is a purchase order class that contains the item components. I've looked at CL_PO_ITEM_HANDLE_MM and CL_PO_HEADER_HANDLE_MM. I couldn't find components as a part of either of the classes.
The second one I'm looking for is not as critical. It is for the components for a production order.   I have a function module: BAPI_PRODORD_GET_DETAIL that gets the components for the order. However, to take advantage of objects - I read somewhere - that if possible I should avoid calling a function module.
Any help that you could give would be greatly appreciated.
Thank you!
Michelle

Hello Michelle
I do not think there are already classes available on ERP 6.0 for reading production order (yet I might be wrong...). However, regarding purchase order you are already on the right track.
*& Report ZUS_SDN_OO_READ_PO
*& Thread: Class for Purchase order item components and Production order components
*& <a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1206523"></a>
"& NOTE: Coding adapted from BAPI_PO_GETDETAIL1
REPORT zus_sdn_oo_read_po.
TYPE-POOLS: abap, mmpur.
PARAMETER:
p_ebeln   TYPE ebeln DEFAULT '3000000045'.
DATA: gs_document    TYPE mepo_document,
      go_po          TYPE REF TO cl_po_header_handle_mm,
      gs_header      TYPE mepoheader,
      gd_tcode       TYPE sy-tcode,
      gd_result      TYPE mmpur_bool.
data: gt_items       type PURCHASE_ORDER_ITEMS,
      gs_itm         type PURCHASE_ORDER_ITEM,
      gs_item        type mepoitem.
START-OF-SELECTION.
* prepare creation of PO instance
gs_document-doc_type    = 'F'.
gs_document-process     = mmpur_po_process.
gs_document-trtyp       = 'A'. " anz. => display
gs_document-doc_key(10) = p_ebeln.
* object creation and initialization
** l_ebeln = purchaseorder.
CREATE OBJECT go_po.
CALL METHOD go_po->po_initialize( im_document = gs_document ).
CALL METHOD go_po->set_po_number( im_po_number = p_ebeln ).
CALL METHOD go_po->set_state( cl_po_header_handle_mm=>c_available ).
* read purchase order from database
gd_tcode = 'ME23N'.
CALL METHOD go_po->po_read
    EXPORTING
      im_tcode     = gd_tcode
      im_trtyp     = gs_document-trtyp
      im_aktyp     = gs_document-trtyp
      im_po_number = p_ebeln
      im_document = gs_document
    IMPORTING
      ex_result    = gd_result.
* there was a problem in reading the PO
IF ( gd_result EQ mmpur_no ).
**    l_messages = l_handler->get_list_for_bapi( ).
**    PERFORM return TABLES l_messages return
**                          poitem poschedule poaccount.
**    CALL METHOD l_po->po_close( ).
ELSE.
    gs_header = go_po->if_purchase_order_mm~get_data( ).
    WRITE: / gs_header-ebeln,
             gs_header-bukrs,
             gs_header-bsart,
             gs_header-lifnr.
ENDIF.
gt_items = go_po->if_purchase_order_mm~get_items( ).
LOOP AT gt_items INTO gs_itm.
    gs_item = gs_itm-item->get_data( ).
    write: / gs_item-ebelp,
             gs_item-matnr,
             gs_item-menge.
ENDLOOP.
END-OF-SELECTION.
Regards
Uwe

Define new document type for purchase order

Hello
I want to create a new document type for purchase ordre with also new number range.
And within my conditions, the shopping card will be generate either document type ECPO with number range 44 or document type ZOS with number range 33.
The document type is still a purchase order.
Is it possible to do that? To assign new document type for purcharse order?
If yes, is there any Badi to put my conditions of generation of my document type?
Thank you for your help.
Regards,
Peggy

Hi Markus
Thank you four your response. Unfortuntly, i do not want to create a new transaction type.
It is still a purchase order which could be visibled in standard transaction. The behaviour is still like standard PO, and could be visible in standard transaction PO.
I just want to create 2 types of purchases orders to identify them, so create a new number range and so a new document type for purchase order..
I have a condition to do "the shopping card will be created in this document type, and this schopping card will be created in this document type".
But standard document type is ECPO, and I don't really know if it is possible to create new document type for purchase order...
Peggy.

Condition Type for Purchase order

Dear All,
I have one query about condition type at item detail level in purchase order.
Please let me know how to disable any condition type for purchase order.
I have already tried it in, SPRO->Materials Management->Purchasing->Purchase Order->Define Screen Layout at Document Level.
But not found it there.
Regards,
Mahesh Wagh

Dear Ganti,
>OMF4 - Materials Management >Purchasing > Purchase Order Processing >Define screen layout at document level
1. No such T Code OMF4 found (I ma using ECC 6.0)
2. NO Such Customizing Menu path sound in SPRO.
Pls elaborate......
Regards,
Mahesh Wagh

IDOC type for interface between SAP ECC and SAP F&R

Hi Experts,
I need SAP standatd IDOC type for interfacing between SAP ECC and SAP F&R [SAP Forecasting and Replenishment] using message type u201CFRE_LOC_SITEu201D.
Please help me in finding the idoc type?
Regards,
Krishan

Hi Denish,
You have 2 ways of loading data from R/3 to APO.
1. R/3 to BW cube to APO-BW cube to APO planning area
or
2. R/3 to APO-BW cube to APO planning area
BW can be a enterprise BW system ( independent) or you can use the BW inbuilt in APO also referred to as APO-BW.
The only difference between the 2 BW systems is APO-BW can not take the load of reporting where as the enterprise BW can.
Unless your company policy requires the enterprie BW system, I suggest using 2nd way.
You can load the data from R/3 to APO-BW cube using extractors either generic or standard depending on your data. You need to have a RFC connection setup between APO-BW and R/3. ( This is not CIF).
When you load the data into the APO-BW cube, you just have to load the data from the cube to APO planning area using the transaction /sapapo/tscube.
Refer to [DP Data Mart|http://help.sap.com/saphelp_scm50/helpdata/en/13/5ada58309111d398250000e8a49608/frameset.htm] for more information about the data transfer between APO-BW and APO.

Purchase orders created have automatically good receipt

hello,
I wish that Purchase orders created have automatically good receipt. What is the manipulation to be made? Thanks for your help.

Hi
U have to do setting movement wise in SPRO
Path SPRO-Material Management -Inventory Management and Physical Inventory - Good Receipts- Automatic Purchase Order Creation
But if you want to do automatic GR receipt u have to write customised program for creation of GR ( May be check BADI - Craeation for MIGO is useful) nand run batch job for the same
Edited by: Sanjay Shah on Feb 8, 2010 3:28 PM

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

Problem in using output type for purchase order

Hi experts,
I am using output type for first time so may be i have done wrong configuration for po output type.The steps i have done are :-
1) Going to tcode NACE->Selected the row u201CEF Purchase Orderu201D and clicked on u201CProcedures".
2) In procedures there are 2 procedures for the application EF (Purchase Order). To proceed further, we would need to find out the procedure that is currently active.Gone to transaction SPRO. In this, navigate as Materials management -> Purchasing ->Messages -> Output control -> Message Determination Schemas ->Define Message Schema for Purchase Order
3) Clicking on u201CAssign Schema to Purchase Orderu201D. So, the procedure RMBEF1 is active for EF (Purchase Order) .
4) Go back to transaction NACE. Select u2018EFu2019 and click on u201COutput typesu201D.
5) Let us use the output type u201CNEU name purchase orderu201D for this purpose. Double-click on NEU.
6) Ensured that the checkboxes u201CAccess to conditionsu201D and u201Cmultiple issuingu201D are checked and the access sequence is 0001(DocType/PurchOrg/Vendor).Only 0001 and 0002 is available in f4 help for this.
7) Now clicked on u201CProcessing Routinesu201D on the left hand side. Ensured that there is an entry for Medium u2018Au2019 (Distribution ALE).
8) After that going back to the main screen of NACE. Select EF (Purchase Order) and clicked on u201CCondition Recordsu201D.
Select NEU and clicked on u201CCondition recordsu201D. The pop-up box appears that gives three radio button option :-
1) Purchasing output determination :purchasing org / vendor for EDI
2) Purchasing output determination :doc. type / purchasing org /vendor
3) Purchasing output determination :document type
but it is not having option only for purchasing organisation through which we can send idoc for changes or creation of PO in that particular pur.org now if i choose 2) i have to give doc type and purchasing org both bcoz they are mandatory fields and value for vendor.
9) Also i have done the necessary ALE configuration (not covered in this document). In the partner profiles, use the message type u201CORDERSu201D and the IDOC type u201CORDERS05u201D.In the tab u201CMessage Controlu201D, used the process codes u201CME10u201D and u201CME11u201D for u201CPO Createu201D and u201CPO Changeu201D respectively.
but the idoc is not generated many times when po is changed and when once it is generated it is giving error
Please suggest solution.
Thanks in advance
nehavt

In me22n in messages tab after looking into processing log it is giving->No recipient found for message type ORDCHG in the
ALE model ,next time giving error as no idoc items belonging to purchasing document found,when i changed message type to ORDCHG the status is green in messages tab it is giving-> error occured while idoc xyz is sent and in WE02 status is red 02
error passing data to port(could not find code page for receiving system)

Inbound Delivery Idoc processing for Purchase Order

We are trying to create a Inbound Delivery for purchase order. We are using idoc basic type DELVRY03.
When we are processing this Idoc we are constantly getting error :
Item 00000 of purchasing document does not exist
Message no. ME706
Diagnosis
Purchase order 00000 with item was not found.
Procedure
Enter a different purchase order.
We have mapped the PO and PO Item fields to Idoc segment fields E1EDL24-VGBEL and VGPOS respectively.
Let me know if anyone came across or know the reason for this message and remdy.
Thanks in advance.

Hi Milind,
Did you get this to work?
Thanks,
Finbarr

Debugging EDI output (IDOC creation) for purchase order...

Hi,
We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
Regards,
Rajesh

Hi
Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
Save.
Set the break point in your user exit.
Go to se 38 -> Run RSNAST00,
Give the object id (Your PO #)
Give the output type and execute, the control will stop at break point.
Regards,
Baburaj

BAPI for Purchase Order Vendor Confirmations

Can any body suggest me the BAPI for the purchase order vendor confirmations transaction code me22n - Tab<b>-(Confirmations)</b> alone.
regs,
Raja

Dear Asha,
Pls find the below code, this handles only the BDC part of the program.Updates only the EKES table thru standard confirmation tab on ME22N.
Kindly clarify any doubts in this reg.
regs,
Raja.
FORM ins_stdtable .
DATA:var TYPE c LENGTH 30,
cstr(02) TYPE n value '01'.
data istr(02) type n value '00'.
DATA recno TYPE i.
data: eblc type c length 5,
ebli type i.
DATA: kebeln LIKE utab-ebeln.
DATA: BEGIN OF indx,
         ebelp type ekes-ebelp,
         eindx type i,
        END OF indx.
DATA : CNT TYPE I value 1.
DATA: COUNTER(2) TYPE N VALUE '01',
ROWS TYPE P.
DATA: w_textout            LIKE t100-text.
DATA: gd_update TYPE i,
        gd_lines TYPE i.
data :waek like indx,
itabek LIKE TABLE OF waek.
*Used to stores error information from CALL TRANSACTION Function Module
DATA: BEGIN OF messtab OCCURS 0.
          INCLUDE STRUCTURE bdcmsgcoll.
DATA: END OF messtab.
SELECT MAX( ETENS ) FROM ekes INTO zetens WHERE ebeln =
ekko-ebeln.
recno = zetens.
LOOP AT utab.
    SELECT distinct ebelp INTO CORRESPONDING FIELDS OF TABLE
    itabek FROM eket WHERE ebeln = ekko-ebeln.
    loop at itabek into waek.
      ebli = ebli + 1.
      waek-eindx = ebli.
      modify itabek from waek.
    endloop.
    loop at itabek into waek where ebelp = utab-ebelp.
      eblc = waek-eindx.
      condense eblc.
    endloop.
    AT NEW ebeln.
      PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0014'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=MECHOB'.
      PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0002'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=MEOK'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'MEPO_SELECT-EBELN'.
      PERFORM bdc_field       USING 'MEPO_SELECT-EBELN'
                                     utab-ebeln.
      AT New EBELP.
        perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
        perform bdc_field       using 'BDC_CURSOR'
                                  'DYN_6000-LIST'.
        perform bdc_field       using 'DYN_6000-LIST'
                                 eblc.
        perform bdc_field       using 'BDC_OKCODE'
                                      '=DDOWN3200'.
        PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0014'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=TABIDT15'.
        perform bdc_field       using 'DYN_6000-LIST'
                                eblc.
        PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0014'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      'PICK'.
      ENDAT.
    ENDAT.
    PERFORM bdc_field       USING 'DYN_6000-LIST'
                                      eblc.
    recno = recno + 1.
    cstr = recno.
    counter = cstr.
*This is to check whether the scheduled line item exceeding 12 rows. if so, use *page up
    if counter >= 13.
      rows = counter MOD 13.
      istr = ( ( counter - rows ) / 13 ).
      do istr times.
        perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
        perform bdc_field       using 'BDC_OKCODE'
                                '=EINB_CREATE'.
      enddo.
      DO 2 TIMES.
        perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
        perform bdc_field       using 'BDC_OKCODE'
                                '=P+'.
      enddo.
      COUNTER = '03'.
      cstr = '03'.
    ENDIF.
    CONCATENATE 'EKES-EBTYP(' cstr ')' INTO var.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                      var.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
    PERFORM bdc_field       USING var
                                utab-ebtyp.
    CONCATENATE 'RM06E-EEIND(' cstr ')' INTO var.
    PERFORM bdc_field       USING var
                                   utab-eeind.
    CONCATENATE 'EKES-MENGE(' cstr ')' INTO var.
    PERFORM bdc_field       USING var
                                   utab-menge.
    CONCATENATE 'J_3ASZDI-J_3ASIZED(' cstr ')' INTO var.
    PERFORM bdc_field       USING var
                                   utab-j_3asize.
    AT END OF Ebelp.
      PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0014'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=MESAVE'.
      perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
      perform bdc_field       using 'BDC_OKCODE'
                                '/00'.
      CALL TRANSACTION 'ME22N' USING bdcdata MODE 'E'.
      IF sy-subrc EQ 0.
        savedone = 'Y'.
        saveflag = 'Y'.
        initflag = 'N'.
        MESSAGE 'SAVED' TYPE 'I'.
      else.
        saveflag = 'N'.
        savedone = 'N'.
        initflag = 'Y'.
        MESSAGE 'Not Saved' Type 'I'.
      endif.
      CLEAR: bdcdata.
      REFRESH bdcdata.
    ENDAT.
ENDLOOP.
ENDFORM.
Hope this will help u

IDOC Types for Purchase Orders, Vendor Master and Goods Receipt

Similar Messages

Maybe you are looking for