Account for purchase orders

Hello to everyone,
how can I set in display mode the account number in a purchase order at item level?, because now it is possible to modify the value that appears by default.
Regards

Go to OME9 and select the a/c category you use for PO and double click on it
here locate the G/L aaccount field and make it display
now if oyu want for more than one A/C category than do same for all.

Similar Messages

Acct determination for Account-assigned purchase order with keys not define

Hi,
I'm trying to post an IDOC of type BBPIV through XI to an R/3 system.
The posted idoc in R/3 is in status 51 (Application document not posted) with the error message "Acct determination for Account-assigned purchase order with keys not defined in chart of acts WP2P"
As per my understanding this is something related to FI.
Long text of the error is "The system cannot generate an automatic posting because there is no account determination defined for Account-assigned purchase order with keys in chart of accounts WP2P.
Correct the account determination for Account-assigned purchase order"
Please help me how to solve this.
Regards,
Rashmi

Hiya,
This looks like its a MM posting / transaction.
You need to go to OBYC and maintain the account assignment. If you provide the business scenario (GR into Stock, Subcontracting, etc.) for the process, I may be able to help.
VKOA is for SD account assignment and I don't believe you can use that here.
Cheers.

Goods Receipt for Account-assigned Purchase Orders

Hello,
We want to make Goods Receipt for Account-assigned Purchase Orders. When we try, SAP gives the error 'Account determination for entry PCOA KBS 0001 not possible'. According to SAP online help, account assignment is adopted from the purchase orders for the transaction/event 'KBS' and we cannot assign transaction key 'KBS' to an account using transaction OBYC. How do you make it work? Any solution pointers will be appreciated and rewarded.
Thanks,
Venu

create an implicit enhancement point in function module CKMV_AC_DOCUMENT_CREATE.
IN STRUCTURE IT_ACCIT U CAN MODIFY THE gl ACCOUNT IN RUN TIME .

SAP how to determine the account in Goods receipt for purchase order?

We know when we make a Goods receipt for purchase order,we will use the account in GBB and BSX define in OBYC. But where can we find the rule? I mean why system can find the account in GBB and BSX , not the other TEcode?

HI
This is again based on the movement type which SAP has created a link internally.
So if you see when a document is posted it basically derives the GL accounts based on the Movement type,Valuation class,valaution area and so on.
Good luck
Hari

GTS 7.2 - Error with account assigned purchase order without material

All,
I am creating an account assigned purchase order without any material master in the feeder system (ECC 5.0) and it a standard SAP functionality.
I am getting the following GTS related pop up message and documents are posted to technically incomplete documents in GTS 7.2.
"Legal Control: Custs Prod. Mast. Required
Material "
Any ideas on how get rid of this error message
Edited by: James Puzon on Oct 3, 2008 9:32 PM

James,
Even though material numbers are not mandatory on POs in the feeder system (ie in ECC) they ARE mandatory in SAP-GTS.
This means that every line item (PO, SO, delivery) that is sent to GTS for compliance screening or Customs processing MUST have a material number in the feeder system. You have a couple of options to resolve this:
1. Always use a material number on all transactions that you enter in your feeder system if they are exports or imports (ie relevant for GTS). You can create service materials or "dummy" materials in ECC for items such as user manuals, warranties or installation services that are part of a particular shipment.
2. You can add logic in the interface for GTS to always transfer a particular material number to GTS if the material number is blank on the line item of the feeder system document. Ideally you would want to link this custom logic to a custom maintenance table in ECC so that you can easily change the material number that is sent to GTS without having to change the code.
3. Override the error message by changing the message type to a warning or informational message (not recommended because this would require a small code modification because I don't think the message type is configurable for this error). Even if you did make this code change you would likely run into more issues in GTS because license determination and other GTS services need a material number to function properly.
Hope this helps.
Sascha

Significance of account assigned purchase order

Dear Gurus,
I would like to know the significance of account assigned purchase order in detail. Also kindly explain the difference between account assigned po and standard po.Thank you.

Hi,
Normally we will use account assigned PO's for Procuring Non-stock & Non-valuated materials.
For ex: consumable materials such as stationary items, spares etc.. we wont take into stock rather we will directly issue to the cost centers since these are low value items.
There are different kind of account assignments such as Consumables (K-Cost Center), Assets - A, Order - F(internal Order) etc.
By using above account assignments value of the materials will be directly posted to the respective G/L in the account assignment.
Whereas Standard PO's are one created for materials which we will take into stock & valuation will be done @ plant level
Thanks & Regards,

Account-assigned purchase order KBS is not activated

Hi Friends,
please expalin me maintain FI configuration; automatic postings procedures Account-assigned purchase order KBS transction account detemination is not activated.
Thanks
E.vasu

Hi,
KBS only define posting key (to which account the postings to happaen).In any account assign purchase order, system prompted to enter GL account (and CO object), which defined the account posting. Ex: Check in OMJJ - For mvt type 101 - update control - GR for acct. assgt. (consumption indicator V with quantity and value updation) - system defines postings as KBS and WRX, KBS refers to the consumption GL account.
KBS key doesnt require any additional settings in OBYC. It only looks for account specification in PO (say K /C/P) and GL account and can be assigned in OKB9 T.code.When we do GR for PO with account assign {KBS (consumption)}, it will debit the given GL account (assigned in OKB9 t.code) and credit GR/IR account (which define in OBYC).
Regards,
Biju K

Getting errors when iam using BAPI_PO_CREATE1 for Purchase Order creation

Hi sap Gurus,
I am getting Errors when iam using BAPI_PO_CREATE1 for Purchase Order creation that Material (144) does not exist but it is alreardy maintained in MM01.
I dont get how it is coming.and what are the mandatory fields in bapi BAPI_PO_CREATE1 in item level .that is too material only.
pls let me know .
thanks in advance.

Hi,
Check the sample code..
report zpo_test             .
*DATA DECLARATION
constants : c_x value 'X'.
*Structures to hold PO header data
data : header like bapimepoheader ,
headerx like bapimepoheaderx .
*Structures to hold PO account data
data : account like bapimepoaccount occurs 0 with header line ,
accountx like bapimepoaccountx occurs 0 with header line .
*Internal Tables to hold PO ITEM DATA
data : item like bapimepoitem occurs 0 with header line,
itemx like bapimepoitemx occurs 0 with header line,
*Internal table to hold messages from BAPI call
return like bapiret2 occurs 0 with header line,
*Internal table to hold messages from BAPI call
pocontractlimits like bapiesucc occurs 0 with header line.
data : w_header(40) value 'PO Header',
purchaseorder like bapimepoheader-po_number,
delivery_date like bapimeposchedule-delivery_date.
data : ws_langu like sy-langu.
*text-001 = 'PO Header' - define as text element
selection-screen begin of block b1 with frame title text-001.
parameters : company like header-comp_code default '122' ,
doctyp like header-doc_type default 'NB' ,
cdate like header-creat_date default sy-datum ,
vendor like header-vendor default '2000000012' ,
pur_org like header-purch_org default 'PU01' ,
pur_grp like header-pur_group default '005' .
*sociedad like HEADER-COMP_CODE default '122' ,
*vendedor like HEADER-SALES_PERS default 'sale person'.
selection-screen end of block b1.
selection-screen begin of block b2 with frame title text-002.
parameters : item_num like item-po_item default '00010',
material like item-material default '12000000' ,
tipo_imp like item-acctasscat default 'K' ,
*pos_doc like ITEM-ITEM_CAT default 'F' ,
shorttxt like item-short_text default 'PRUEBA BAPI' ,
grup_art like item-matl_group default '817230000' ,
plant like item-plant default '3001' ,
mpe like item-trackingno default '9999' ,
*contrato like ITEM-AGREEMENT default '4904000003' ,
*quantity like ITEM-QUANTITY default 1 .
po_unit like item-po_unit default 'EA'.
selection-screen end of block b2.
Par?mnetros de imputaci?n
selection-screen begin of block b3 with frame title text-004.
parameters : centro like account-costcenter default '1220813150',
cuenta like account-gl_account default '6631400' ,
num_pos like account-po_item default '10' ,
serial like account-serial_no default '01' ,
ind_imp like account-tax_code default 'I2' .
selection-screen end of block b3.
start-of-selection.
*DATA POPULATION
ws_langu = sy-langu. "Language variable
*POPULATE HEADER DATA FOR PO
*HEADER-COMP_CODE = sociedad .
header-doc_type = doctyp .
header-vendor = vendor .
header-creat_date = cdate .
header-created_by = 'TD17191' .
header-purch_org = pur_org .
header-pur_group = pur_grp .
header-comp_code = company .
header-langu = ws_langu .
*HEADER-SALES_PERS = vendedor .
*HEADER-CURRENCY = 'DOP' .
*HEADER-ITEM_INTVL = 10 .
*HEADER-PMNTTRMS = 'N30' .
*HEADER-EXCH_RATE = 1 .
*POPULATE HEADER FLAG.
headerx-comp_code = c_x.
headerx-doc_type = c_x.
headerx-vendor = c_x.
headerx-creat_date = c_x.
headerx-created_by = c_x.
headerx-purch_org = c_x.
headerx-pur_group = c_x.
headerx-langu = c_x.
*HEADERX-sales_pers = c_x.
*HEADERX-CURRENCY = c_x.
*HEADER-ITEM_INTVL = c_x.
*HEADER-PMNTTRMS = c_x.
*HEADER-EXCH_RATE = c_x.
*HEADER-EXCH_RATE = c_x.
*POPULATE ITEM DATA.
item-po_item = item_num.
item-quantity = '1'.
*ITEM-MATERIAL = material .
item-short_text = 'prueba bapi_po_create1'.
*ITEM-TAX_CODE = ''.
item-acctasscat = 'K' .
*ITEM-ITEM_CAT = 'D' .
item-matl_group = '817230000' .
item-plant = '3001' .
item-trackingno = '99999'.
item-preq_name = 'test'.
*ITEM-AGREEMENT = '' .
*ITEM-AGMT_ITEM = ''.
item-quantity = '1' .
item-po_unit = 'EA'.
*ITEM-ORDERPR_UN = 'EA'.
item-conv_num1 = '1'.
item-conv_den1 = '1'.
item-net_price = '1000000' .
item-price_unit = '1'.
item-gr_pr_time = '0'.
item-prnt_price = 'X'.
item-unlimited_dlv = 'X'.
item-gr_ind = 'X' .
item-ir_ind = 'X' .
item-gr_basediv = 'X'.
*ITEM-PCKG_NO = '' .
append item. clear item.
*POPULATE ITEM FLAG TABLE
itemx-po_item = item_num.
itemx-po_itemx = c_x.
*ITEMX-MATERIAL = C_X.
itemx-short_text = c_x.
itemx-quantity = c_x.
*ITEMX-TAX_CODE = C_X.
itemx-acctasscat = c_x.
*ITEMX-ITEM_CAT = c_x.
itemx-matl_group = c_x.
itemx-plant = c_x.
itemx-trackingno = c_x.
itemx-preq_name = c_x.
*ITEMX-AGREEMENT = C_X.
*ITEMX-AGMT_ITEM = c_x.
itemx-stge_loc = c_x.
itemx-quantity = c_x.
itemx-po_unit = c_x.
*ITEMX-ORDERPR_UN = C_X.
itemx-conv_num1 = c_x.
itemx-conv_den1 = c_x.
itemx-net_price = c_x.
itemx-price_unit = c_x.
itemx-gr_pr_time = c_x.
itemx-prnt_price = c_x.
itemx-unlimited_dlv = c_x.
itemx-gr_ind = c_x .
itemx-ir_ind = c_x .
itemx-gr_basediv = c_x .
append itemx. clear itemx.
*POPULATE ACCOUNT DATA.
account-po_item = item_num.
account-serial_no = serial .
account-creat_date = sy-datum .
account-costcenter = centro .
account-gl_account = cuenta .
account-gr_rcpt = 'tester'.
append account. clear account.
*POPULATE ACCOUNT FLAG TABLE.
accountx-po_item = item_num .
accountx-po_itemx = c_x .
accountx-serial_no = serial .
accountx-serial_nox = c_x .
accountx-creat_date = c_x .
accountx-costcenter = c_x .
accountx-gl_account = c_x .
account-gr_rcpt = c_x.
append accountx. clear accountx.
*BAPI CALL
call function 'DIALOG_SET_NO_DIALOG'.
call function 'BAPI_PO_CREATE1'
    exporting
      poheader         = header
      poheaderx        = headerx
    importing
      exppurchaseorder = purchaseorder
    tables
      return           = return
      poitem           = item
      poitemx          = itemx
      poaccount        = account
      poaccountx       = accountx.
*Confirm the document creation by calling database COMMIT
call function 'BAPI_TRANSACTION_COMMIT'
exporting
wait = 'X'
IMPORTING
RETURN =
end-of-selection.
*Output the messages returned from BAPI call
loop at return.
    write / return-message.
endloop.
Regards
Sudheer

GL account in Purchase order with account assignmt cat F

Hi,
I am creating a PO with account asignment category F (Internal Order) and entered the Internal Order in account assignemnt category.
but at that time, system is asking for currecny.
We dont want to enter the GL manually so can anyone help me from where this GL will be defaulted.
Thanks,
Sudha

Hi Sudha,
Usually PO of the nature F(internal Order) & K(cost center) are meant to book for services or items/material for which master data doen't exist & they are directly charged to expense. So at the time of creating PO, details of GL, cost center/internal order are entered manually in usual scenario.
However, if you still want to expore the automatic assignment then you can check in Tcode OBYC, transaction type "Account-assigned purchase order - KBS". You have to activate the same & then maintain.
Regards,
Akhil

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
<b>AND</b>
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.

User Exit for Purchase Order Release Strategy

Hi,
I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
Thanks in advance.
Mick

Hi
Check the following Exits and BADI for Pur Requisition
Enhancement
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
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 PO
MM06E008 Monitoring of contr. target value in case of release orders
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 processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
Business Add-in
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED Purchasing Document Posted
SMOD_MRFLB001 Control Items for Contract Release Order
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
Reward points if useful
Rgds,
Naren

User Exit/BADI for Purchase Order and Purchase Requisitions

HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun Bahal

For Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
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
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
Regards,
Anirban

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

"Not possible to determine account for sales order or project stock"

Hi,
I get this error when trying to create a purchase order (type EUB). I think I should define a new account for sales order. How should I proceed?
Thanks in advance.
Luis.

Hi
1) Check the spro-MM-purchasing-account assignment-Maintain account assignment categories -
Here check the account modifications against Account assignment category C,P
2) Then go to OBYC -GBB check the account maintained against the account modifier obtained in step 1
Regards
Sandeep

SAP Rules / Considerations behind ATP for Purchase Orders

Hi
Can anyone guide me to the considerations taken into account for ATP check for Purchase orders,
Kind Regards
Bhavana

Hi,
Please find the logic.
ATP quantity
Specifies the available quantity from each receipt that can still be used to cover further requirements.
Use
The ATP quantity is calculated as follows:
Initially, the ATP quantity of a new receipt is the complete receipt quantity. During the availability check according to ATP logic, the system only takes into account receipts that lie before a requirement. A requirement first reduces the most recent receipt (and thus the ATP quantity of this receipt). If a rest quantity remains for this receipt, this quantity is the new ATP quantity for this receipt and it can be used to cover a further requirement.
If one receipt does not completely cover the requirement, the system reduces further receipts and their ATP quantities until the requirement has been completely covered.
If no further ATP quantity is available to cover a requirement or if a requirement can only be partially covered, then this shortage quantity is displayed in the requirements line as a negative ATP quantity.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/3764f4449a11d188fe0000e8322f96/content.htm
http://help.sap.com/erp2005_ehp_04/helpdata/EN/4c/227d1046e611d189470000e829fbbd/content.htm
and the above links will provide you some idea.
Regards

Account for purchase orders

Similar Messages

Maybe you are looking for