Bapi_po_create1 - enjoy purchase orders

Hi
I am using bapi_po_create1 for purchase orders conversion. I have a problem in using this. Whatever delivery date i supply in bapimeposchedule-delivery_date, it is getting overridden with the default date else current date. would like to have a solution for this problem.
Thanks
Elango

Hi Andrzej
I did fill the respective POSCHEDULEX table with 'X'. I used the date format yyyymmdd. The date value for purchase order create date is working fine. I assume the date field is getting populated based on the INFO records. if i dont fill the the info records it takes current date otherwise based on the info records. Pl let me have some solution for this..
elango

Similar Messages

Enjoy purchase order transaction

Hi All,
Can anybody tell me how get idea on Enjoy Purchase Order.
ie, how to update it ie, using bapi.
Can anybody explain it in detail.
regards,
phaneendra.

Hi,
Check reply from vijay babu using BAPI_PO_CREATE1
BDC for ME21N
Regards

Availability check in Enjoy Purchase Order & Requisition

Hi Experts,
The availability check is used in 4.7E also but what is difference in Ecc 6.0 or new functionality added
Can any one plz let me know
Regards
Pratap

Below is capture from sap release documentation :
Availability Check in Enjoy Purchase Order and Requisition
(Changed)
Use
As of SAP ECC 6.0, SAP_APPL 600, display and checking of availability are invokable separately in the
Enjoy purchase order and requisition in line with the system behavior on the Sales side.
You invoke the display and checking of availability in the Enjoy purchase order (transaction code
ME21N) and the Enjoy purchase requisition (transaction code ME51N) as follows:
- To display the availability overview, choose Environment -> Availability
- To check availability, choose the Check Availability icon.
13.6.16.3 System Behavior After Availability Check for an Item (Changed)
Use
If you carry out the availability check for an item of a stock transport order, hitherto the system adopted
confirmations as per the desired date/time only.
SAP AG 30
______________________________________________________S_A_P_-S_y_s_te_m_
As of SAP ECC 6.0, SAP_APPL 600, you can define in Customizing how the system reacts if the desired
quantity cannot be confirmed for the desired date/time.
You have a choice of two settings:
- Confirmation as per desired date/time
This is the standard setting and corresponds to previous system behavior.
- Delivery proposal
- Full confirmation
Effects on Customizing
You make the settings in the Rule for Adoption of ATP Results in Purchasing field in Customizing for
Purchasing under Purchase Order -> Set Up Stock Transport Order -> Assign Delivery Type and
Checking Rule.

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

New smart form picking enjoy purchase order /SAPDII/SPP_ORDER

Hi Experts,
Ours is a new implementation project.
Requirement is to design a new smart form for purchase order.
The print program for the purchase order is loaded.
When I go for print preview the print program is calling the enjoy PO and not my form.
I checked in the transaction NACE
PRINT PROGRAM : Z_SMBZA_ZA_FM06P
FORM ROUTINE :ENTRY_NEU
FORM : -
PDF/SMARTFORM : Z_MMPO_ZA
My print program has 2 includes
INCLUDE Z_SMBA0_AA_FM06TOP.
INCLUDE Z_SMBA0_AA_FM06PE02.
Every thing is working fine except with the following piece of code
IF NOT tnapr-sform IS INITIAL.
lf_formname = tnapr-sform.
ELSE.
MESSAGE e001(ssfcomposer).
ENDIF.
Here I am getting tnapr-form as /SAPDII/SPP_ORDER and not Z_MMPO_ZA
If I change the field to Z_MMPO_ZA in debugging it works fine and I am getting the output of my form.
In the table TNAPR the field SFORM shows Z_MMPO_ZA
In the table NAST the field PFLD3 shows /SAPDII/SPP_ORDER
Can some one help me how to make the program by default read my form and not /SAPDII/SPP_ORDER
Thanks
Joshi

Hi,
IF NOT tnapr-sform IS INITIAL.
lf_formname = tnapr-sform.
ELSE.
MESSAGE e001(ssfcomposer).
ENDIF.
In debugging check what is value in TNAPR-KSCHL and confirm whether this is the desired output for PO printing.
Also check in PO Header --> Messages, what is the output type configured there. If it is not the desired output type, try adding your desired output type there and chek the print preview.
Also confirm the NACE settings are correct for your Output Type used wihile taking the PO printout.
Thanks & Regards,
Harish

Regarding BAdi : Customer's Own Screens in Enjoy Purchase Order

Hi freinds
If we activate the above mentioned BAdi what enhancements will we get in comparition with std functionality.
Regards
Eldee

Hi
By implement ting this BAdi you can define your own screens which will be visible in ME21n screen at the time of purchase order creation.
Certain screens or fields which are not present in the standard but required by the client can be accomplished using this BAdi.
Thanks & Regards
Kishore

Enjoy Purchase order - Personal settings v Vendor Master fields

We want to use Personal settings to default certain fields but want fields from the vendor master to take prioirty.... can we change the field selection available to users or can we switch off personal settings, or change the priority so if payment terms maintains at vendor level, these take prioity over personal setting ones!

Dear Keith,
You can try it in your system, i told you as per standard SAP, so we talk about SAP design, and for me, it make sense if the personal setting is overriding the vendor master setting, because the vendor master (purchasing data) also just for default data,and SAP give personal setting in order to make default data under user level, so the personal setting is only effected for the user, not all user that using the transaction
Regards,

User exit in enjoy Purchase order transactions -MM06E005

I am trying to write a code in the enhancement MM06E005 - to check a field in the enjoy PO transaction me22n when saving and issue a warning message.
I am using the function module EXIT_SAPMM06E_012 to do this. It does not work. But when I try to make it as an error message, it works.
The warning message can be issued to the me22 using the
same function module and exit.
Our requirement is to generate a warning message in me22n . Any help on this?
Other requirement is to bring up/show a tab on the screen with this message, as it does with SAP standard messages.
Is there any way to do this, if possible how?
thanks

Hi,
what message you are getting is it Program names ZX... are reserved for includes of exit function groups?
Then That message is only a warning, so you can go on: by double click on the include.
press enter, the system'll create the include ZX... where you have to insert your code.
The message is advising you're creating an include for an enhancement.
Regards
Kiran Sure

Implementation Of BADI For Enjoy Purchase Order

I have implemented a 'ME_GUI_PO_CUST' BADI for ME21n. The control is going to Subscribe and Map Dynpro methods. But the control is not going to other methods like TRANSPORT_FROM_MODEL
TRANSPORT_TO_DYNP
TRANSPORT_FROM_DYNP
TRANSPORT_TO_MODEL.
Please explain how we can make the control to move to these methods.
Thanks In Advance.

ME21N - PO Enhancement using BADI

Default text in Purchase Order Header text

Hi,
When i create a PO, only for a specific plant I want a default text description to be captured automatically in the Header Text.
How to get this done?
Please post your inputs.
In case you need any additional info please revert.
Thanks,
Suresh.

Hi
Use this BAdi
The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis.
You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE.
Typical applications for this BAdI include:
Processing of own objects
Processing of additional data on standard objects
Implementation of additional checks and derivations
Change of data in standard fields
Change in field selection
The PROCESS_ITEM method enables you to change the item data and check it for correctness.
Thanks & Regards
Kishore

Purchase Requisition mandatory in Purchase Order

Hi
I have a requirement to configure 5 document types and among that 2 documents types must have PR as mandatory and the remaining 3 document types will not have PR as mandatory.
I've tried in screen variant but it is not working.
kindly let me know the other way to configure the above requirement.
Regards
Bala

Hi Bala
Masa wanted to know, do you want to create the POs in SRM or not. SRM POs also end up reaching ERP in Classic and Extended classic Scenarios.
Try this BADI in ECC ME_PROCESS_PO_CUST, This may help you build some check while using ME21N, ME21 or BAPI_PO_CREATE1 to check what doc type is selected for PO and then you may throw an error if it is not referencing a PR
The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis.
You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE.
Typical applications for this BAdI include:
Processing of own objects
Processing of additional data on standard objects
Implementation of additional checks and derivations
Change of data in standard fields
Note
Ensure that data integrity is guaranteed.
Change in field selection
Regards
Virender Singh

User exit or BADI while saving purchase order

Hello,
I want to use an user exit or BADI while saving of purchase order. The objective is to check the material group of the line item while saving. We don´t want to allow to save purchase orders for one material group.
Can you please guide me.
Thanks
Srinivasan

Hi
The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis.
You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE.
Typical applications for this BAdI include:
Processing of own objects
Processing of additional data on standard objects
Implementation of additional checks and derivationsChange of data in standard fields
Change in field selection
you can use this BADI for checking the material group
Thanks & Regards
Kishore

Purchase Order with Invoice Plan

Hi,
I need to understand working with Invoicing plans for a Purchase Order. Especially the service PO for the rents and other related services.
How the PO is linked to the Invoice Plan and how the process happens in SAP?
Thanks in advance!

Creating an Invoicing Plan
The following procedure describes how to create an invoicing plan with the pre-Enjoy ordering transactions (ME21, ME22, ME23).
The procedure described is also applicable u2013 with certain restrictions u2013 to the Enjoy purchase order (ME21N, ME22N, ME23N).
If you are using the Enjoy purchase order, you will find:
·         The Invoicing Plan button and the indicators for GR-based invoice verification (GR-Based IV), service-based invoice verification (Srv.-Based IV), evaluated receipt settlement (ERS), and invoice receipt (Inv. Receipt) among the item details on the Invoice tab page.
·         The account assignment among the item details on the Account Assignment tab page
·         The Goods Receipt and GR Non-Valuatedindicators among the item details on the Delivery tab page
Prerequisites
Vendor Master Record
Before you can use the invoicing plan with automatic settlement, the Evaluated Receipt Settlement Delivery indicator must be set on the Purchasing Data screen in the vendor master record.
(If you wish to enter invoicing dates manually, this is not necessary.)
Purchase Order
●     We recommend using a framework order (that is a purchase order with a validity period and a reason for rejection). The invoicing plan can adopt the validity period specified in the PO header.
●     PO items for which you wish to use an invoicing plan must have account assignment irrespective of whether a material with a master record, a material described by a short text, or an external service is involved.
●     The GR/IR control facility must be set up in such a way that no goods receipt (or, in the case of services, no service entry) is expected - only an incoming invoice. If you wish to have automatic settlement, you must also set the Evaluated Receipt Settlement indicator.
If you nevertheless wish to allow service entry sheets for the item (e.g. for information purposes only), you must set the GR Non-Val. indicator.
Customizing
Under Purchase Order à Invoicing Plan in Customizing for Purchasing, you can maintain data such as the desired invoicing plan types, date categories, and date descriptions.
Procedure
       1.      Create a purchase order with account assignment (framework order).
Click to access the item overview (or the overview of service lines if you chose item category D for services).
       2.      Enter the desired material or service, the quantity, and the price.
       3.      Select the desired item and click Account Assignments to access the account assignment screen. Enter the account assignment for this item.
       4.      Click to access the item detail screen. Check that the GR/IR control indicators are set correctly on the item detail screen.
○     The GR and GR-Based Invoice Verification or Service-Based Invoice Verification indicators must not be set.
○     IR must be set.
○     You must set ERS if you wish to have Evaluated Receipt Settlement.
○     If you wish to have service entry sheets purely for information, for example, allow non-valuated goods receipt (i.e. select the GR Non-Val and GR indicators).
       5.      Choose Item ® Invoicing Plan. A window appears, in which the invoicing plan types predefined in Customizing are suggested. Choose the desired invoicing plan type and click Continue.
You can use the following invoicing plan types:
○     Periodic Invoicing Plan
■      You use the periodic invoicing plan if the total value of the PO item is to be invoiced in each period.
■      The system creates the invoicing dates automatically on the basis of the settings in Customizing.
■      The invoicing date and the amount to be invoiced are shown for each settlement period (e.g. month). In the case of the periodic invoicing plan, the amount represents the total value of the PO item.
■      You can change the suggested dates and block individual dates for automatic invoicing if necessary.
■      You can enter the start and end dates for the invoicing plan.
■      With the Dates from and Dates to fields, you can determine that an invoicing plan does not contain invoicing dates extending over the entire validity period of the purchase order but only for a certain period within that validity period. (E.g. within a validity period from 1.1. to 12.31, only dates within the period 1.1. to 06.30.)
■      With the Horizon field, you control how far into the future dates can be created. If you enter a date rule that adds six months to the current date here, invoicing dates will be created for just half a year in advance in each case.
The system automatically creates new dates if you change the invoicing plan or when you invoke the transaction for Updating Periodic Invoicing Plans. See Generating Further Invoicing Plan Dates
■      The In Advance indicator allows you to specify whether the invoice is to be created with regard to a prior or subsequent period. (E.g. at the beginning of February, either in advance for the month of February or in arrears for the month of January).
■      In addition, fields with information on the existing invoicing plan are displayed (e.g. the calendar upon which the date determination process is based).
○     Partial Invoicing Plan
■      You use the partial invoicing plan if the total value of the PO item is to be invoiced in several partial amounts.
■      You get an empty date overview in which you can manually enter the desired dates.
■      If you work with a reference invoicing plan, the system automatically generates dates in accordance with the reference plan.
You have the following options:
●      You create a reference invoicing plan in Customizing for the invoicing plan type.
●      You enter an existing invoicing plan as reference plan directly in the invoicing plan for the PO item.
■      You can flag a date in field B (Billing/Invoicing Rule) as follows:
●      As a down payment (percentage or value)
●      As an invoicing date (percentage or value)
●      As a final invoice
       6.      Click to return to the item overview.
       7.      Click to save the purchase order item with the invoicing plan.
You can then start the automatic invoice creation process during invoice verification.
For more information, refer to the section Settlement of Amounts Due Under Invoicing Plans.
Once assigned to an item, the invoicing plan type (e.g. partial invoicing plan) cannot be changed. If you wish to assign a different invoicing plan type, you must delete the item and create a new one.
Generating Further Invoicing Plan Dates
If you have assigned a periodic invoicing plan to a PO item but have not initially defined invoicing dates covering the entire validity period of the purchase order, you can generate further dates in due course.
You have created a PO item with a periodic invoicing plan for a certain planned procurement. The purchase order is valid from 1.1. to 12.31. When creating the invoicing plan, you specified one invoicing date per month for the first half of the year. You have not yet planned any dates for the second half of the year because you do not wish information from the invoicing plan to be passed on to purchase order commitments at this stage, for example.
By mid-June, it is clear that the PO is to proceed as envisaged, and you therefore wish to schedule invoicing dates for the remainder of its validity period.
Procedure
To schedule further invoicing dates, proceed as follows:
Choose Purchase order ® Follow-on functions ® Period. invoicing plan
Specify the purchase orders for which invoicing dates are to be generated in the invoicing plan and perform the function.
A log can be created if desired.
Result
The system adds further dates on the basis of information such as the validity period or horizon from Customizing, the purchase order, and the invoicing plan.
regards,
indranil

Purchase order on Hold is not working from Sales Order document

Hello gurus,
I'm detecting a problem that I have.
I have created a Sales Order and then, this document create a Purchase Requisition in automatic.
So, when I create the purchase order, adopting the purchase requisition, I want to save this as on Hold.
The problem is that the button "Hold" is missing.
But, if I create a purchase requisition and I register the sales order directly (account assignment "E") and then, I create the purchase order, adopting the purchase requisition, the button "Hold" is not missing.
I have active the BADI to Hold, but, it is only mention restrictions with Third Party and Services, not with Sales Order normal.
Could you help me please a.s.a.p.?
Regards,
Sandra Palomo

Application component: MM-PUR-PO-GUI
Function group: MEPO
The Business Add-In (BAdI) ME_HOLD_PO enables you to specify whether an
Enjoy purchase order can be put on hold or whether this function is to be
suppressed in accordance with your requirements.
In the standard system, this function is generally offered during the
creation of an Enjoy purchase order (transaction ME21N) and when a PO
that is on hold is changed (transaction ME22N).
Note
Enjoy purchase orders cannot be put on hold if any of the following
criteria apply:
o The PO contains service items
o The PO contains "third-party" items
o Commitment errors are involved
o Subsequent (period-end volume rebate) settlement is involved
In the case of stock transfers within a company code, the "Hold" function
is generally inactive. If an application object contains an error of any
kind, the function is likewise inactive.

Purchase Order Header Text.

Dear all,
We maintain the header text in PO. There are around 10 different text items in the PO header text.
All these 10 text items are nearly same for some vendors( around say 300 vendors) when purchases are made from these vendors.
Please note that it is not for all vendors and not for material vendor combination (Not in Info records) but only vendor specific.
My requirement is that is it possible to configure system so that when i create the PO for any one of 300 vendor system should automatically put/insert those header text items.
i.e. 300 Vendors-----> Common PO Header Text
Regards,
SP

Hi
Either you can carry out the Process as specified above or.
Create a Z table for the 10 Text Objects & maintain them.
Create another Z table & Maintain the Vendors
Use the Business Add-In (BAdI) ME_PROCESS_PO_CUST , which enables you to extend the business logic of the Enjoy purchase order on an individual basis.
Use the method Process_HEADER
Maintain the Logic of populating the Texts based on the Vendor.
Thanks & Regards
Kishore

Bapi_po_create1 - enjoy purchase orders

Similar Messages

Maybe you are looking for