Starting Conditions for Purchase Order WF

Hi all,
We have developed a Workflow (Process-Controlled Workflow) for SRM Purchase Order. The requirement we have is that if the PO is released and then changed, only the WF should start again if the amount is changed. Any other field change in the PO should not trigger WF again.
There is customizing to define which fields should trigger WF for Shopping Cart, but I don´t found this for Purchase Order:
PRO--> SRM server --> sourcing--> Define Fields in Shopping Cart Which Trigger Workflow
Any suggestions?
Many thanks,
Ezequiel

Hi,
In your scenario 1, if system is saying that there the PO has to be approved, it means that you have managed the user that will receive the workitem..
Activating all PO WF is not a solution as in standard there are two many cases activated (amount, role, limit...)
I propose you to first activate only the 0 step WF and to overwrite the code inside
Just code that every PO modification should trigger O step WF thus it will be more simple to test it.
Later on, if you want to implement more complex starting conditions, you just have to modify the WF content...
Kind regards,
Yann

Similar Messages

Activating conditions for Purchase Order workflows in EBP

Dear SRMer's,
I am facing the following problem:
System Info :SRM Server 5.5, ECC 6.0
Scenario 1:
All start conditions for Purchase Order in SAP Business Workflow are activated.
I created a direct procurement shopping cart (DP) in SRM browser and ordered it, then I logged in as proffessional purchaser, changed the Price and processed the DP PO.
When Ordering, the follow on Documents are created, but says the PO is waiting for approval. When I check for this PO in the Backend R/3 system in the Me22n (Display PO changes), I don't see the PO.
Scenario 2:
All Start conditions for Purchase Order in SAP Business Workflow are de-activated
I created another direct procurement shopping cart (DP2) in SRM browser and ordered it, then I logged in as proffessional purchaser, changed the Price and processed the DP2 PO (Status is held).
When Ordering, I get the Warning message, no workflow found, contact system administrator.
Please advice what needs to be configured for the PO to be ordered successfully.
Thanks in advance
Raj

Hi,
In your scenario 1, if system is saying that there the PO has to be approved, it means that you have managed the user that will receive the workitem..
Activating all PO WF is not a solution as in standard there are two many cases activated (amount, role, limit...)
I propose you to first activate only the 0 step WF and to overwrite the code inside
Just code that every PO modification should trigger O step WF thus it will be more simple to test it.
Later on, if you want to implement more complex starting conditions, you just have to modify the WF content...
Kind regards,
Yann

Invalidate condition for purchase order

Hello,
we have a manual condition which we used in purchase orders (FRA2) which shouldn't be used anymore. Accidently from time to time it's still getting entered which results in wrong postings.
Is there a way (e. g. valid date, ...) to forbid the use of an condition in new purchase orders? (customizing, somewhere else?).
I don't want to delete it as it's still in use in some old PO's... (if it's possible to delete - don't have a clue).
Thanks in advance.
BR,
Hansi

Hello Hansi,
Thanks for your feedback..
Yes you can prohibit through:
Goto MEK2 transaction -> Slect the Matrial Inforecord -> enter the required details
Line item level you have option of Validity to - give the back date.
One more thing: SPRO -> Define condtion type (we have option) -> Master Data tab -> Valid From and Valid to option.
Please check this option also. i have not tried this..
BR
Suneel Kumar

ECS: New Pricing condition for purchase order on item level

Hello Experts,
we use SRM 5.0 with the extend classic scenario.
We customized a new pricing condition (absolute discount), which we want to use in a purchase order and added it to the calculation schema.
condition type:
Application     BBP
Source system LOCAL
Usage           PR
Condition Type ZRBT
Access Seq.     01CT
Condition class       discount
Calculat. Type    fixed amount
Condit.category
Rounding rule commercial
manual has priority
item level
delete
amount/percent
UoM
Scale Base Type   quantity
Check stat             none
Max. No. Dimens    no scales
We see the condition type and can choose it in the transaction which is used to create a po.
But when we choose it from the drop-down box it isn't added to the calculation.
Regards,
Sven

Hello Sven,
Thank you very much for posting the OSS note solution for your issue.
I had similar issue and finally was able to resolve it after reading your post.
regards
Vinod

Header Condition for Purchase Order Services

Hi All,
It´s possible to add a header/item condition at service level, that will be charged in total at the first service entry sheet for that service?
Thanks in advance,
Tiago Ferreira

Hello Tiago,
As per note 353482 it is possible to maintain header condition on the SERVICE OUTLINE LEVEL.
This note explains what condition types are available.
Best regards,
Eduardo Junior

Table name for purchase order delivery fields

Hi Gurus,
Can you please tell me the name of the tables and the joining condition for purchase order delivery details like Name, street , city, postal code, address detail and the joining condition?
Regards
MD. SAMY

Hi MD. SAMY,
1. Table EKPO has details lat line item level.
2. You must make a simple ABAP program in the infosets (or functional area) that contain a line "addrnumber = ekpo-adrnr" while addrnumber is ADRC table field.
3. Choose fields that you want in ADRC and put it into new fields (e.g. : DELI_NAME2 = adrc-name2., etc)
4. The new field attribute must be maintained in the infosets (in EXSTRA).
5. Now in the query you have those fields.
Regards,
Sameer

Change Pricing for purchase order

Hello All,
FOR STO deliveries, we want to aportionate freight charges in case of multiple POs. Our inbound idoc sends only one order and calls BAPI_PO_CHANGE.
we are trying to update Pricing condition of other related purchase orders belonging to same delivery in a user exit. User exit is SAPL2012. Is there any function module to update Pricing conditions for purchase orders?
BAPI_PO_CHANGE would not work here as this userexit is called in this BAPI.
Any suggestion?

Any suggestiions?

Purchasing condition for sales order costing

I am trying to add a condition to a purchasing document calculation schema that retrieves the sales order cost for a configurable material. I am using account assignment of M for this purchase order and have tried several settings in a conditin type. But no cost is ever found. Has anyone ever tried this?

Hi Arpit,
1. Go to t-code SWO1.
2. Click Settings -> Delegate.
3. Delegate the BO YBUS2032 to the BO BUS2032.
In workflow perform the following steps:
1. Go to t-code SWDD and open your workflow template.
2. Go to Basic Data (cap sign button at the top of the screen) or click Ctrl + F8
3. Go to Start Events tab.
4. In the Object type enter your BO name BUS2032 (not YBUS2032), in Event of object enter the BO event.
5. Click on 'B' i.e. Binding Defined, click on generate automatic binding. It would automatically generate the appropriate binding for the workflow. You can also alter the binding as per requirement.
6. Click on 'C' i.e. Start Condition. A dialog would open, select the appropriate start condition for the workflow. Use the attribute that you created and make the start condition. Check the condition before saving (recommended).
6. Click on 'A' to Activate the binding and start condition. All 'A', 'B' and 'C' would get green.
7. Save the changes made and activate your workflow.
Hope this helps!
Regards,
Saumya

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

Where pricing condition P101 is maintained for purchase order

where pricing condition P101 is maintained for purchase order
by which t code

Are you looking for the transaction where you maintain condition records or contition types???
Transaction: MEK1 for Condition record Creation - Purchasing...
and Navigation Path for maintain Purchasing conditions types is:
IMG->Materials Management->Purchasing->Condition->Define Price Determination Process->Define Condition Types...
Hope this helps.
Kind Regards
Eswar

Creating an IDOC for purchase order

Hello gurus,
I want to generate an IDOC for purchase order.
The Logical System, RFC connection, ports definition is already defined.
In my system i have 800 client as source/sender and 100 client as target/reciever.
On Outbound side-> In Partner profile
I defined-
1. Partner No.- devclnt100
2.Type- US (User)
3. Agent - SAPUSER
In Outbound parameters-
I created message type as Orders.
One thing to note that my partner system is LS i.e. Logical System
Then in Outbound Options-
I mentioned Reciver Port - 800Port
Output Mode- I selected "Transfer Idocs immediately"
& "Do not start subsystem"
In Idoc type-
I gave following information-
Basic Type - Orders05
In Message Control tab i mentioned-
Application - EF
Message Type - NEU
Process Code - ME10
In NACE Transaction Code-
I selected EF Purchase Order as my condition for output control
In that- In output types-
I selecte NEU and double clicked. I checked whether Access to Conditions check box is checked and multiple issuing is checked.
In Dialog structure-Processing routines I checked that -
For Output type - NEU
Application - EF
Processing routines are defined-
medium-Distribution ALE
Program -RSNASTED
Form Routine - ALE_PROCESSING
I think these are the very basic settings that need to be done for creation of Idoc.
Now when i create a PO and then SAVE it an IDOC must be generated.
But when i go to transaction Code WE02. It shows me message "No Idocs genereated".
What is the problem? Where am i going wrong?

Hi Yayati,
Here are all the settings that you need to do. I am not sure which all settings are present so kindly confirm.
Sending side Client800:
1. WE20 - under LS - Outbound parameters - message type = Orders , basic type = Orders05
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
3. NACE - App = EF - Output Types - Processing Routines - Add medium = A (Distribution (ALE)) , Program = RSNASTED, Routine = ALE_PROCESSING.
4. NACE - App = EF - Output Types - Partner Functions - Add medium = Distribution (ALE), Funct = VN.
5. Name - App = EF - Condition Records - Output type = NEU , Choose ur combination (Mine is DocType/Purc Grp)
Pur.Doc Type = NB (Execute) , Add row Medium = A ,Function = VN and other details u choose.
Receiving side Client100:
1. WE20 - under LS - Inbound parameters - message type : Orders ; Process Code : ORDE
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
For the PO which you have created, go to the PO in ME23N, click on messages .
There should be a line : Output = NEU, Medium = Distribution (ALE)... etc.
If its present then the configuration was correct.
If it has a yellow triangle means it was not processed.
Regards,
Jovito.
Edited by: dsouzajovito on Dec 30, 2010 10:24 AM

Open items for purchase order its very urgent

hi
my requirement is to write extract program for purchase order(me21) to extract only open items.
please provide sample code its very urgent.
thanks in advance.
points will be rewarded.
thanks
hari prasad reddy

check the below report :
REPORT ZMM_OPEN_PO_REPORT no standard page heading
                          line-size 255
                          message-id zwave.
======================================================================
Program Name : ZMM_OPEN_PO_REPORT                                    *
Description : This report displays all Open PO Items and output     *
               would be PO Number,Material number and so on          *
Author       : Seshu                                                 *
Date         : 01/24/2007                                            *
MODIFICATION HISTORY                                                 *
DATE    | AUTHOR   | CHANGE #   | DESCRIPTION OF MODIFICATION        *
--|||--
01/24/07| Seshu    | DEVK921979 | Initial                            *
D A T A D E C L A R A T I O N   P A R T                         ***
type-pools
type-pools : slis.
Tables
tables : ekko, " Purchase order Header
         ekpo, " Purchase order Item
         marc. " Material with Plant data
Internal table for output.
data : begin of i_output occurs 0,
       ebeln like ekko-ebeln,
       matnr like ekpo-matnr,
       end of i_output.
ALV Data declaration.
data : v_repid like sy-repid.
ALV Function Module Variables
DATA: gs_layout type slis_layout_alv,
      g_exit_caused_by_caller,
      gs_exit_caused_by_user type slis_exit_by_user.
DATA: gt_fieldcat    type slis_t_fieldcat_alv,
      gs_print       type slis_print_alv,
      gt_events      type slis_t_event,
      gt_list_top_of_page type slis_t_listheader,
      g_status_set   type slis_formname value 'PF_STATUS_SET',
      g_user_command type slis_formname value 'USER_COMMAND',
      g_top_of_page type slis_formname value 'TOP_OF_PAGE',
      g_top_of_list type slis_formname value 'TOP_OF_LIST',
      g_end_of_list type slis_formname value 'END_OF_LIST',
      g_variant LIKE disvariant,
      g_save(1) TYPE c,
      g_tabname_header TYPE slis_tabname,
      g_tabname_item   TYPE slis_tabname,
      g_exit(1) TYPE c,
      gx_variant LIKE disvariant.
data : gr_layout_bck type slis_layout_alv.
Ranges
ranges r_eindt for eket-eindt.
initialization.
v_repid = sy-repid.
start-of-selection.
Get the data from EKKO ,EKPO and MARC Table
perform get_data_tables.
end-of-selection.
display the data in the form of ALV
perform display_data.
*&      Form get_data_tables
      Get the data from EKKO,EKPO and MARC Table
FORM get_data_tables.
clear : i_output.
refresh : i_output.
fill the dates in ranges
r_eindt-low = sy-datum - 7.
r_eindt-high = sy-datum + 14.
r_eindt-option = 'BT'.
r_eindt-sign = 'I'.
append r_eindt.
Get the data from EKKO,EKPO and EKET Tables
select aebeln bmatnr into table i_output
                       from ekko as a inner join
                            ekpo as b on aebeln = bebeln
                            inner join marc as c on cmatnr = bmatnr
                            inner join mara as d on dmatnr = bmatnr
                            inner join eket as e on eebeln = aebeln
                                           and   eebelp = bebelp
                            where c~beskz = 'E'
                            and   c~werks = '1000'
                            and   d~mtart = 'FERT'
                            and   b~loekz = space
                            and   b~elikz = space
                            and   e~eindt in r_eindt.
if sy-subrc ne 0.
message e000(zwave) with 'No open purchase order found'.
endif.
ENDFORM.                    " get_data_tables
*&      Form display_data
      text
FORM display_data.
Fill the Fiedlcat
PERFORM fieldcat_init using gt_fieldcat[].
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
   I_INTERFACE_CHECK                 = ' '
   I_BYPASSING_BUFFER                =
   I_BUFFER_ACTIVE                   = ' '
     I_CALLBACK_PROGRAM                = v_repid
   I_CALLBACK_PF_STATUS_SET          = ' '
    I_CALLBACK_USER_COMMAND           = g_user_command
   I_CALLBACK_TOP_OF_PAGE            = ' '
   I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
   I_CALLBACK_HTML_END_OF_LIST       = ' '
   I_STRUCTURE_NAME                  =
   I_BACKGROUND_ID                   = ' '
   I_GRID_TITLE                      =
   I_GRID_SETTINGS                   =
   IS_LAYOUT                         = gr_layout_bck
      IT_FIELDCAT                       = gt_fieldcat[]
   IT_EXCLUDING                      =
   IT_SPECIAL_GROUPS                 =
   IT_SORT                           =
   IT_FILTER                         =
   IS_SEL_HIDE                       =
   I_DEFAULT                         = 'X'
    I_SAVE                            = g_save
    IS_VARIANT                        =
   IT_EVENTS                         =
   IT_EVENT_EXIT                     =
   IS_PRINT                          =
   IS_REPREP_ID                      =
   I_SCREEN_START_COLUMN             = 0
   I_SCREEN_START_LINE               = 0
   I_SCREEN_END_COLUMN               = 0
   I_SCREEN_END_LINE                 = 0
   IT_ALV_GRAPHICS                   =
   IT_ADD_FIELDCAT                   =
   IT_HYPERLINK                      =
   I_HTML_HEIGHT_TOP                 =
   I_HTML_HEIGHT_END                 =
   IT_EXCEPT_QINFO                   =
IMPORTING
   E_EXIT_CAUSED_BY_CALLER           =
   ES_EXIT_CAUSED_BY_USER            =
    TABLES
      T_OUTTAB                          = i_output
   EXCEPTIONS
     PROGRAM_ERROR                     = 1
     OTHERS                            = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " display_data
*&      Form fieldcat_init
      text
     -->P_GT_FIELDCAT[] text
FORM fieldcat_init USING e01_lt_fieldcat type slis_t_fieldcat_alv.
DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
Purchase order number
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'EBELN'.
LS_FIELDCAT-ref_fieldname = 'EBELN'.
LS_FIELDCAT-ref_tabname = 'EKKO'.
LS_FIELDCAT-TABNAME    = 'I_OUTPUT'.
ls_fieldcat-seltext_L = 'Purchase Order'.
ls_fieldcat-seltext_M = 'Purchase Order'.
ls_fieldcat-seltext_S = 'Purchase Order'.
APPEND LS_FIELDCAT TO E01_LT_FIELDCAT.
Material #
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'MATNR'.
LS_FIELDCAT-ref_fieldname = 'MATNR'.
LS_FIELDCAT-ref_tabname = 'EKPO'.
LS_FIELDCAT-TABNAME    = 'I_OUTPUT'.
ls_fieldcat-seltext_L = 'Material'.
ls_fieldcat-seltext_M = 'Material'.
ls_fieldcat-seltext_S = 'Material'.
APPEND LS_FIELDCAT TO E01_LT_FIELDCAT.
ENDFORM.                    " fieldcat_init

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

Menu path - for goods receipt for purchase order (MB01)

Hi
What is the menu path for Goods receipt for purchase order (MB01) - ECC6.0

hi
the path is too deep
plz just log in ur system and find MB01
Materials Management > Purchasing > Master Data > Subsequent Settlement > Vendor Rebate Arrangements > Environment > Condition/Arrangement > Environment >Pricing > Environment Value assignment > Inventory management > Goods receipt >For purchase order > MB01 - PO number known
regards
KI

Pricing Procedure for Purchase Order

I have to pick item level conditions for value : bed , hr edu cess, edu cess, cst,lst.
I am trying to the pick up fields kbetr and kwert for following conditions from konv table but there are only header level conditons.
so How can i Proceed for this?
For Purchase order script i have used standard Program SAPFM06P.But this a subroutine Pool Program.

hi
Write a Sub-routine in the form, where u can call all the pricing procedures.
write this in the form
/:           PERFORM TAX_AMT IN PROGRAM ZMM_REP_POTAX
/:           USING &EKPO-NETWR& .
/:           CHANGING *xxx-xxx&
write a sub-routine in abap editor , calling the program name and calculating pricing procedures
regards
sailendra kolakaluri

Starting Conditions for Purchase Order WF

Similar Messages

Maybe you are looking for