PROCESS CODE FOR PURCHASE ORDER

Hi Friends,
what is the process code for Purchase order... because i need to creating a partner profile in WE20 in the inbound side.. if iselect message type ORDERS menas.. that related.. process code( for purchase order is not displaying)..
can any of you give me the Message type and that related Process code for purchase order..
thanks
Babu

Hi Babu,
You will find out the all Process Code from WE41 for Outbound & WE42 for Inbound.
The Process code for ORDERS: Purchase order is ME10 for Outbound and you can find it out the message type for Inbound from WE42.
If need more info let me know..
Cheers
Veera

Similar Messages

Specific process code for Production order message type LOIPRO

Hello,
Is there any specific process code for Production order message type LOIPRO.
Request you to reply.
Thanks
Prashanth

Hi Prashanth,
sorry for last thread ... that not contain full information ...
For message type LOIPRO you can use process code APLI.
In IDOC PARTNER definition, the partner is linked with an IDOC TYPE and PROCESS CODE for inbound processing. This process code is in turn linked with a FUNCTION MODULE to process the IDoc such as IDOC_INPUT_INVOIC_MRM (Reff.. http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_cid519558,00.html)
Regards,
Amit

BAPI for updating tax code for purchase order..

Hi friends,
I have one requirement to change tax code for multiple Purchase order but the
thing is they should not go for release.So what should I prefer BDC or BAPI.
I am thinking to implement it through BAPI, but I don't know what procedure to follow.
If somebody can provide me a small guiding steps or code then it will be very helpful for me..
Thnaks in advance..
Useful answers will be rewarded with points....
Regards,
Rajesh Akarte

Hi Friend,
BAPI_ACC_PURCHASE_ORDER_CHECK Accounting: Check Purchase Order
BAPI_ACC_PURCHASE_ORDER_POST Accounting: Post Purchase Order
MEWP BAPIs Purchase order
BAPI_PO_CREATE Create Purchase Order
BAPI_PO_GETDETAIL Display Purchase Order Details
BAPI_PO_GETITEMS List Purchase Order Items
BAPI_PO_GETITEMSREL List Purchase Orders for Release (Approval): New as of 4.0A
BAPI_PO_GETRELINFO Display Detailed Release (Approval) Information on Purchase Order
BAPI_PO_GET_LIST List Purchase Orders - Only up to 4.0A
BAPI_PROCOPERATION_GETCATALOGS Determine Valid Catalogs as Value Help
BAPI_PROCOPERATION_GETINFO Analysis of Objects to be Generated in Purchasing
AND
Use condition type NAVS with access sequence 0003 to default the taxcode in the purchase order item using conditions. Materials Management -> Purchasing -> Purchasing order processing ->define screen layout at document level. Search for the transaction ME21.Double click on ME21. Then search for TaxCode
Use condition type NAVS with access sequence 0003 to default the taxcode in the purchase order item using conditions.
A2: Go to IMG.
Materials Management -> Purchasing -> Purchasing order processing ->define screen layout at document level.
Search for the transaction ME21.Double click on ME21. Then search for TaxCode. It is advisable to configure also the info record. The tax code should be a required entry, and whatever you specify here will be the default value in the Purchase order.
Materials Management -> Purchasing -> Purchasing info record -> define screen layout.
When you get here you search for the transaction ME12 ,double click here; search for Input VAT indicator.
Regards ,
Kumar.

Transaction Code for Purchase Order with Network, Activity, and Element

I have been asked for a transaction code that will allow the user to view the Purchase Order, Network, Activity, and Element on the same transaction. I have been able to use CN41 to get them the Purchase Requisition, Network, Activity, and Element, but cannot seem to find one for the Purchase Order.
I feel like this should be easy...
Any ideas?

Hi,
I would recommend you to test BAdI ME_PROCESS_PO_CUST.
Regards,
Edit

System Variable or Process code for Sales Order create/Change

Hi All,
 I have a wriiten custom routine (routine no 901) for Pricing in VOFM.Now the thing is the code is written in such a way that, the routine will be called only for transaction VA01 and VA02.But If i want the routine(901) to be executed also through BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_SALESORDER_CHANGE ,then what system parameter i should check in my routine.
Currently the code is like this.
form frm_kondi_wert_901.
Check sy-tocde = 'VA01' or sy-tcode = 'VA02'.
*Process further'....
Endform.
I would appreciate for the valuable input....
Thanks,
Vigneswaran S

Awesome stuff sudhir..It is really a great logic to use..Thanks for ur help..
This is for future generation...
One Note:The field symbol should be declared as type any instead of "standard table".Because the T181 is used as global workarea(strucuture) in SAPMV45A program rather than internal table.
Here you go the modified code.
FIELD-SYMBOLS:<fs_t180> TYPE any .
DATA:wa_t180 TYPE t180,
 c_t180(15) TYPE c VALUE '(SAPMV45A)T180'.
ASSIGN (c_t180) to <fs_t180>.
 wa_t180 = <fs_t180>.
If wa_t180-tcode = 'VA01' or wa_t180-tcode = 'VA02'.
Endif.
Thanks,
Vigneswaran S

Idoc for purchasing order

can any1 explain the steps needed to send a purchase order through ALE/IDOCS
pls explain it with reference to PURCHASE ORDER

Hi,
cehck the same...
This method is used for distributing transaction data like purchase order, sales order etc.
In this method the extra transaction code that we use is we41 (outbound process code) and we use this in the message control tab in the partner profiles.
The transaction codes that are required for this method are
We81
We30
We31
We82
We21
We20
Bd64
Nace
Me22n (purchase order), va02 (sales order) etc.
Ex: purchase order.
Message type: ORDERS
Idoc type: ORDERS05
Outbound process code for purchase order: me10
The steps that are to be followed are:
Check for the message type in the transaction in we81.
check for the idoc type in the transaction we30.
check we82 in which the link between message type and idoc type is there.
create the port in we21.
Configure the partner profiles in we20.
Click on the + button outbound parameters and give the message type, receiver port
Idoc type.
Now press on the message control tab, this is the place where u give the outbound process code. The message type in the message control is the output type that is used in the nace transaction.
Create a distribution model in bd64.
Go to purchase order transaction (me22n).and press the messages tab
In the messages tab give the output type and the distribution medium as distribution-ale and then save it.
Reward if helpful.
Regards,
Nagaraj

Process code for 869(EDI ) Order Status Inquiry Message type.

Hi Gurus,
Please can any one help in providing Process Code for 869 Order Status Inquiry Message type.
Thanks,
Sudhakar

Hi Everybody.
There's no standard process code for LOIPRO Outbound Idocs.
This Idocs are threated as master data info, and could only be automatically generated by Data Distribution Model.
BD64.
Anyway, you can define your own Outbound Process Code in WE41 using CLOI_MASTERIDOC_CREATE_LOIPRO FM.
You can choose.
Regards.
Albert.

What Message type and Process Code to use for Purchase Order Change in 4.6C

I like to implement in SAP R/3 4.6C a scenario for Purchase Order Change, via inbound IDoc.
I have been searching, but could not find what Message Type, Idoc Basic Type and Process Code to use.
I can not imagine this functionality does not exist in 4.6C.
Any suggestions for my problem are welcome.

Hello,
In this case you should use the message PORDCH and BAPI method BAPI_PO_CHANGE but only exist as of release 4.7.
Function module    BAPI_IDOC_INPUT1
Idoc Type              PORDCH01
Message Type      PORDCH
So check carefully the following OSS notes:
[Notes 589066 - BAPI_PO_CHANGE: Incorrect account assignment to network |https://service.sap.com/sap/support/notes/589066] (not be fooled by the description)
[ Notes 197958 - BAPIs for purchase orders - Missing Functions|https://service.sap.com/sap/support/notes/197958]
Regards,
Andrea
Edited by: Andrea Olivieri on Sep 3, 2009 10:17 AM

I found a exit CIFPUR02 for purchase order inbound process.is it suitable?

I found a exit CIFPUR02 for purchase order inbound process.is it suitable?
my idoc is PORDCR102 AND message type is PORDCR1. my requirement is this is EXIT should trigger before saving the data in me21n.
Edited by: rk.kolisetty on Jun 24, 2010 4:59 PM

Hi,
Following are the user exit relevant to T Code ME21n.
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMEKO001 Extend communications structure KOMK for pricing
LMEKO002 Extend communications structure KOMP for pricing
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Rgd,
Chetan

Processing log output for Purchase order

Dear All,
Iam getting some problem when iam creating an IDOC and checking in the Processing log for IDOC number.
Actually i had created one custom idoc for Purchase order since my client need only some field and in one line for header and line item, I had done it and i can see it in sdata of EDIDD structure. When i create a Purchase order and save it an idoc number is posting and I can see this file in my physical directory indeed.
Now when iam going into change mode of PO ME22n to see the Processing LOG, It is not showing the IDOC Number in Purchase order output processing log popup.

The processing log will only show output based standard output control (Table NAST).
How is your IDoc being created. Via a user exit, BADI. If so then they will not appear on the processing log.
It is being created as a custom IDOC for which i had written a Z function module and given that in PO processing code which is ME10. When iam checking the standard IDOC for PO it is generating the IDOC in processing log as well.
Iam just placing my code just have a look at it and suggest if any thing needs to be done.
FUNCTION Z_IDOC_OUTPUT_ORDERS.
""Local Interface:
*" IMPORTING
*" VALUE(OBJECT) LIKE NAST STRUCTURE NAST
*" VALUE(CONTROL_RECORD_IN) LIKE EDIDC STRUCTURE EDIDC
*" EXPORTING
*" VALUE(OBJECT_TYPE) LIKE WFAS1-ASGTP
*" VALUE(CONTROL_RECORD_OUT) LIKE EDIDC STRUCTURE EDIDC
*" TABLES
*" INT_EDIDD STRUCTURE EDIDD
*" EXCEPTIONS
*" ERROR_MESSAGE_RECEIVED
*" DATA_NOT_RELEVANT_FOR_SENDING
DATA: xdruvo. "Druckvorgang
DATA: neu VALUE '1', "Neudruck
 h_kappl LIKE nast-kappl, "Hilfsfeld Applikation
 h_parvw LIKE ekpa-parvw, "Hilfsfeld Partnerrolle
 h_ebeln LIKE ekko-ebeln. "Hilfsfeld Belegnummer
CLEAR control_record_out.
 xdruvo = neu.
h_kappl = object-kappl.
h_ebeln = object-objky.
h_parvw = object-parvw.
DATA:
 LT_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE,
 L_EDIDC LIKE EDIDC,
 L_SEND_FLAG,
 W_SDATA LIKE EDIDD-SDATA.
DATA: T_BDI_MODEL LIKE BDI_MODEL OCCURS 0 WITH HEADER LINE.
DATA: T_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
DATA: T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA: C_MESSAGE_TYPE LIKE EDIDC-MESTYP VALUE 'ZORDER'.
*- Call function module to determine if message is to be distributed
OBJECT_TYPE = 'BUS2012'.
MOVE control_record_in TO control_record_out.
CALL FUNCTION 'ALE_MODEL_DETERMINE_IF_TO_SEND'
 EXPORTING
 MESSAGE_TYPE = C_MESSAGE_TYPE
 IMPORTING
 IDOC_MUST_BE_SENT = L_SEND_FLAG.
 EXCEPTIONS
 OWN_SYSTEM_NOT_DEFINED = 1
 OTHERS = 2.
DATA : BEGIN OF EKKO_tAB OCCURS 0,
EBELN LIKE EKKO-EBELN,
F1 TYPE C VALUE ',',
BUKRS LIKE EKKO-BUKRS,
F2 TYPE C VALUE ',',
BSART LIKE EKKO-BSART,
F3 TYPE C VALUE ',',
LIFNR LIKE EKKO-LIFNR,
F4 TYPE C VALUE ',',
WAERS LIKE EKKO-WAERS,
F5 TYPE C VALUE ',',
BEDAT LIKE EKKO-BEDAT,
F6 TYPE C VALUE ',',
WERKS LIKE EKPO-WERKS,
F7 TYPE C VALUE ',',
PLIFZ LIKE EKPO-PLIFZ,
F8 TYPE C VALUE ',',
EBELP LIKE EKPO-EBELP,
F9 TYPE C VALUE ',',
MATNR LIKE EKPO-MATNR,
F10 TYPE C VALUE ',',
MENGE LIKE EKPO-MENGE,
F11 TYPE C VALUE ',',
MEINS LIKE EKPO-MEINS,
F12 TYPE C VALUE ',',
END OF EKKO_TAB.
DATA SDATA1 LIKE EKKO_tAB OCCURS 0 WITH HEADER LINE.
DATA EBELN LIKE EKKO-EBELN.
WRITE OBJECT-OBJKY TO EBELN.
SELECT T1EBELN T1BUKRS BSART LIFNR WAERS BEDAT WERKS PLIFZ EBELP MATNR MENGE MEINS
FROM EKKO AS T1
INNER JOIN EKPO AS T2 ON T2EBELN = t1EBELN
INTO CORRESPONDING FIELDS OF TABLE EKKO_tAB
WHERE
*T1~KAPPL = 'EF' AND
T1~EBELN = EBELN.
*T1~KSCHL = 'YEDI' .
DATA SDATA LIKE EDIDD-SDATA.
DATA NDATE LIKE SY-DATUM.
DATA NMENGE(17) TYPE C.
LOOP AT EKKO_tAB.
 WRITE EKKO_TAB-MENGE TO NMENGE.
 NDATE = EKKO_tAB-BEDAT + EKKO_tAB-PLIFZ.
 CONCATENATE EKKO_tAB-EBELP ',' EKKO_tAB-BUKRS ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-LIFNR ',' EKKO_tAB-BEDAT ','
 NDATE ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-EBELN ', 0,' EKKO_tAB-MATNR ','
 NMENGE ',' EKKO_tAB-MEINS ',' EKKO_tAB-WERKS INTO SDATA.
 MOVE SDATA TO: W_SDATA, T_EDIDD-SDATA.
 MOVE 'ZORDERS' TO T_EDIDD-SEGNAM.
 APPEND T_EDIDD.
ENDLOOP.
*call function 'L_IDOC_SEGMENT_CREATE'
 exporting
 i_segnam = 'ZORDERS'
 i_sdata = w_sdata
 exceptions
 others = 1.
*LT_EDIDC
call function 'L_IDOC_SEND'
 tables
 t_comm_idoc = LT_EDIDC
 exceptions
 error_distribute_idoc = 1
 others = 2.
*DATA T_BDI_MODEL LIKE BDI_MODEL.
WRITE OBJECT-OBJKY TO T_BDI_MODEL.
READ TABLE T_BDI_MODEL INDEX 1. " maximum 1 recipient
L_EDIDC-DIRECT = 1.
L_EDIDC-DOCNUM = DOCNUM. "***
L_EDIDC-RCVPRN = 'HCM_00_785'.
L_EDIDC-RCVPOR = 'MM_PO_FILO'.
MOVE 'ZORDER' TO L_EDIDC-MESTYP.
MOVE 'ZPURIDOC' TO L_EDIDC-IDOCTP.
MOVE 'LS' TO L_EDIDC-RCVPRT.
MOVE T_BDI_MODEL-RCVSYSTEM TO L_EDIDC-RCVPRN.
*MOVE-CORRESPONDING L_EDIDC TO W_EDIDC.
*- Distribute the iDoc
BREAK-POINT.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' "IN UPDATE TASK
 EXPORTING
 MASTER_IDOC_CONTROL = L_EDIDC
 TABLES
 COMMUNICATION_IDOC_CONTROL = LT_EDIDC
 MASTER_IDOC_DATA = T_EDIDD
 EXCEPTIONS
 ERROR_IN_IDOC_CONTROL = 01
 ERROR_WRITING_IDOC_STATUS = 02
 ERROR_IN_IDOC_DATA = 03
 SENDING_LOGICAL_SYSTEM_UNKNOWN = 04.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE LT_EDIDC INDEX 1.
control_record_out-direct = '1'.
CONTROL_RECORD_OUT-DOCNUM = DOCNUM. " ***
control_record_out-serial = sy-datum.
control_record_out-serial+8 = sy-uzeit.
control_record_out-mestyp = LT_EDIDC-mestyp.
control_record_out-idoctp = LT_EDIDC-idoctp.
control_record_out-SNDPRN = 'HCM_00_786'.
MOVE 'MM_PO_FILO' TO control_record_out-RCVPOR.
MOVE 'LI' TO control_record_out-SNDPRT.
MOVE 'SAPQIS' TO control_record_out-SNDPOR.
ENDFUNCTION.

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

Process Code for Outbound Production Order??

Does anybody know the Process Code for Outbound Production Order??
BASIC Type : LOIPRO01
Message Type : LOIPRO
Regards,
Ravi

Hi Everybody.
There's no standard process code for LOIPRO Outbound Idocs.
This Idocs are threated as master data info, and could only be automatically generated by Data Distribution Model.
BD64.
Anyway, you can define your own Outbound Process Code in WE41 using CLOI_MASTERIDOC_CREATE_LOIPRO FM.
You can choose.
Regards.
Albert.

Different No Range for Purchase orders - company code wise.

Dear All,
Hi.
at present we have just one company code in the server.
now we are getting second company code in the same server, for this new coopany code. business needs seperate no range for purchase orders.
so please guide me how i can configure in the system
Thanks
h shah

Here
we are going to use same document type.
is it possible to use any user exit???
Thanks
h shah

T.Code for Release Procedure for Purchase Order Type

Hi Frd
im working in ECC 6.0.
OMGS is t.code for Release Procedure for Purchase Order Type in SAP 4.6.
Can anyone tell me what is the t.code for Release Procedure for Purchase Order Type in ECC 6.0 .the OMGS t.code is not working in ECC.
Thanks
By
Pari

Hi Rajasekharan,
Go to tcode ME22 and enter the Purchase order number.
inside the Display screen,u can see a GREEN flag button on the Application Toolbar.
Click on a item and press the Green Button.
U will see the release code,provided the Purchase order is set to release strategy,after that Go to tocde ME28 enter the release code ,along with Document number and then release the Purchase order.
Actually the tcode for releasing purchase order is ME28
Reward points if useful.
Cheers,
Swamy Kunche

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)

PROCESS CODE FOR PURCHASE ORDER

Similar Messages

Maybe you are looking for