Change in Rejection flag for purchase orders (PO) - Output determination

Hi all,
I hope you can help me with this issue:
We are using table T166C to specify which fields should be consider when you change them in a PO. That means only that changes should determine output message. However, it seems SAP is always determining output message when you change field EKPO-ABSKZ (Confirmations Rejection). It doesn't matter if you manage that field in T166C or not, it seems to be done by standard.
As a summary: we don't want that SAP considers that change in ABSKZ field as a change.
Maybe I am wrong in any of my affirmations. If true, it would be great if you can guide me about which steps or tables should be used. If I am right, I don't know how can I do that SAP avoid to check this field as a change (I tried with several possibilities but maybe I have been working for the same issue for a long time and my eyes cannot see the solution although it is in front of me)
Any help or comment will be very appreciated.
Thanks in advance.
David.

Hi Uday,
This is a standard functionality, if you are increasing the amount in PO, release stretegy will always gets trigers, wheater change is small or big.
but at the same time if you are decreasing the amount in PO release will not get trigger till the time your approbal level is not changing.
let say in your case: you have final release at $ 3 milion, and the second last approval at $ 2 Million.
and PO has value $ 2.8 million.
now if you change price from 2.8 to 2.5 miilion. release will not get active.
but if you change price from 2.8 to 1.99 million. this release will get trigger.
hope this will help you.
regards,
vikas
as you discribed, you have final release on 3 million dollar

Similar Messages

How to know which Smart-Form is being used for Purchase Order print output

Hi Gurus ,
How to find which Smart-Form and and methods/program being used for Purchase Order print output in SRM ?
In ECC we have tcode NACE where we can check all the details.Is there something similar in SRM ?
Please help.
Regards,
Saurav

There is no similar transaction in SRM for your purpose. Usually if the customers customize the smartforms, they would choose to use their own form by implementing BADI BBP_OUTPUT_CHANGE_SF. Take a look into your system and see if this BADI is implemented. If so, debug it (by pressing "Print Preview" for a PO for example) and find out what form it is using. Or, if the BADI is not implemented, by default, the system uses form BBP_PO.

Need a field for purchase order quantity

We need a field that is fixed once the PO is created and is never updated even if the qty is changed later on.

Hi Chandra
Not clear with your query...
Are you looking for a field to act as a constant where you can store the PO Item Quantity which was initially created???
If so, not really sure on the reason but you can get the orginal qty value from Change Documents.
OBJECTID for Purchase Orders is EINKBELEG.
Kind Regards
Eswar

Reg.Output type for purchase order

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

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

Output Message Determination for Purchase Order

Hi all !
Can anybody please explain in brief, the procedure for Ouyput message determination for Purchase order. (including printer settings)
I have tried it throgh the Standard Configuration guide. but i am not able to do.
Please explain step by step including form attachment.
Thanks in Advance !!!!

Hi,
Customization steps for Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
Note1
Now Check in SPAD (Printer settings) settings & try to check the printer configuration. Check Device attributes, Access methods etc. are maintained in Spool Administration (SPAD) for the selected printer (your local Printer, may be ur using HP01or any but in SAP std is LP01) but consult with your basis consultant regarding above.
Check the following also:
Spool generated using SP01 or SP02.
Output device.
Local printer settings.
Paper Tray, Print Mode, Printer
Note2:
Check MN04 and NACE t.codes
Regards,
Biju K

HOT TO SET THE OUT PUT MESSAGE FOR PURCHASE ORDER

As i was saving the Purchase order in Me21n the error message that came up was " NO OUTPUT MESSAGE SET FOR THE PO " HOW DO I SET THE OUTPUT MESSAGE AND SET THE PO PRINT SETTING KINDLY HELP.

Hi
First of all Execute program RSNAST0F in SA38 .
Following are some steps for PO message printing
Maintain Output of Purchase Order
1. Condition Table
SPRO  Material Management-> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Ex:
EF---> ZNEU
Select ZNEU and double click on Mail title and texts and go to
EN- New Purchase Order Print Out,
Select ZNEU again and double click on Processing routines,
Select ZNEU again and double click on Partner Roles
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
ZNEU -> ZNB
Now you create PO(ME21N) and maintain the text and save it. Go to ME22N and print the PO by giving output type ZNEU).
Vishal...

Searching for Workflow for Purchase Order Change

Hi experts!
We are using SRM5.0 / extended classic scenario and backend R/3 4.7 Enterprise.
We should implement an approver process for the purchase order changes. Does any one of you know whether there exists a standard SAP workflow?
Many thanks for your help.
Regards,
Corinne

Hi
Please refer to the following links for detailed step-by-step details.
Workflows for Purchase Orders - n-step approval workflow ( WS14000145 )... Start WS14000075, WS14000089 or WS14000145...-step approval workflow ( WS14000145 )
http://help.sap.com/saphelp_srm50/helpdata/en/5a/c5173f5ff48443e10000000a114084/frameset.htm
Authorization - Purchase orders ( WS14000145 )
http://help.sap.com/saphelp_srm50/helpdata/en/f7/a6a3415e34b05fe10000000a1550b0/frameset.htm
Setting Up SAP Business Workflow - WS14000145 ( n-step approval )... WS14000145... WS14000145 N-step approval PO WS14000145 N-step approval of contract
http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
Dynamic Modification - Purchase orders ( WS14000145 )
http://help.sap.com/saphelp_srm50/helpdata/en/84/dda441e79ead5fe10000000a1550b0/frameset.htm
Back & Forth Processing and the Retain Function - Purchase orders ( WS14000145 ) 
http://help.sap.com/saphelp_srm50/helpdata/en/6b/eca441eea7ef0be10000000a1550b0/frameset.htm
Approval Workflows for Purchase Orders and Change Versions
http://help.sap.com/saphelp_srm50/helpdata/en/ec/fe163ff8519a06e10000000a114084/frameset.htm
Workflow for Contracts - Workflow for Purchase Orders ( WS14000145 )
http://help.sap.com/saphelp_srm50/helpdata/en/26/0f8b41ed891609e10000000a155106/frameset.htm
SRM Business Workflow - One-step Approval
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm
WS14000089
http://help.sap.com/saphelp_srm50/helpdata/en/5a/c5173f5ff48443e10000000a114084/frameset.htm
WS14000075
http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5a/af5efc85d011d2b42d006094b92d37/frameset.htm
Regards
- Atul

Incorrect message type in IDOC for Purchase order change

Hi Gurus.
Please advise on below.
We have several purchase orders that are configured to trigger IDOC upon change. But accidentally, someone has deactiveted the automatic proposal of EDI message type for these Purchase orders which resulted to not transmitting purchase order change documents automatically.
As a workaround, we have proposed to create EDI message manually during Purchase order change. But upon checking in tcode WE09, message type is ORDERS which is PO create instead if ORDCHG for purchase order change.
Please kindly advice on why it is behaving like this for purchase orders with EDI message previously deactivated.
Thanks in advance.
Acel.
To simulate.
Create PO. go to messages, select EDI message then deactivate permanently. Save PO. Release PO if needed. Change PO. go to messages, EDI is not automatically proposed. create EDI message mamanually. Save PO. Release PO id needed. check tcode WE09, for PO create, no IDOC since it was deactivated permanently. For PO change, IDOC was triggered but with incorrect message type ORDERS instead of ORDCHG.

Hi Acel,
You will need to check the settings in transaction WE20 - You will be using a Partner Profile to determine the outbound message, either for each vendor or a generic one.
on the outbound parameters, you will need to ensure that ORDCHG is set up as a message type. If not, add it, ensuring that you use the message ORDCHG, the basic type (or extension) that you are using, usually ORDERS05 and make sure that in message control, you have process code ME02 set up. This should enable the correct message type to be determined.
Regards,
Rob

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

Is there any function module for purchase order change

Hi Experts,
Is there any function module for purchase order change or i need to do new recording in me22n.
Thanks,
Senthil

Hi
Function module BAPI_PO_CHANGE enables you to change purchase orders. The Change method uses the technology behind transaction ME22N.
Regards,
Viven

How to implement Change pointers for Purchase order - ME22N - Custom Fields

Hi Experts,
Can you please tell me how to implement - Change Pointer for Custom fields in IDOC.
I am working on IDOC - For purchase order - acknowledgements - in custom screen/tab in ME22N.
Everything is working fine according to my requirement.
All i need to know is the process of - Creating/Change - Change pointers for Custom fields.
1.How to implement change pointers for custom fields.
2.Can we maintain - Change Document - for custom fields at data element level?
P.S. - I have browsed many previous - forums before posting a new discussion.
please share your inputs...
explaining how to create/implement - change pointers for custom fields will help me .
Regards,
Karthik Rali.

Hi,
To maintain Change Document for custom field:
1. Check if "Change document" checkbox is set in data element.
2. Find Change Document Object for transaction.
   You can use SQL trace - ST05.
   Look there for line with table CDHDR and statement insert values
   (for example for transaction KA02 Change Document Object is KSTAR)
3. Regenerate update program for this Change Document Object in transaction SCDO
Change documents for z-fields schould be generated.
I am not sure about change pointers but they are configured somehow in BD61 and BD50.

Workflow for purchase order rejection and esclation.

Hi,
Can any body tell us the what is the standard workflow for purchase order rejection and esclation.
if no standard WF is there then how can create the workflow for ecslation and rejection.
Thanks & Regards,
Priti shrivastava

Please check here.
http://help.sap.com/saphelp_srm30/helpdata/en/5a/c5173f5ff48443e10000000a114084/content.htm

Activate Change Pointers for Purchase Orders

I thought that change pointers would be active by default for purchase orders, but when I change a purchase order field that should be change pointer enabled, nothing is written in table BDCP.
Here's what I have done:
1) Used transaction SCDO to look at the change Documents.
2) Identified object EINKBELEG (Purchasing Document) as the likely object.
3) Verified that table EKKO is one of the tables in the object.
4) Verified that the data element of the field that I am changing in the PO - ZBD2T - is change pointer enabled (it is).
I cannot get any entry created in BDCP with these settings; change pointers are working for other documents.
I also put a breakpoint on the sebugger for the function module EINKBELEG_WRITE_DOCUMENT in the update task, and I cannot see it being triggered, so I am wondering if I am doing the correct thing here.
Can somebody please tell me what I am doing wrong?
BR,
Tony.

Hi Guys,
This issue was solved by implementing the BTE 4005 (OPEN_FI_PERFORM_00004005_E). This particular event is triggered in the update task for saving changes to business object. So In my function module (corresponding to BTE), I have explicitly called the method to write an entry in COM_SE_CPOINTER, because we just need the reference of business object for which classification data is changed.
Please refer the below code for more clarity.
BTE position: -
method called in FM to write change pointer.
Thanks anyways, for all the responses.
Cheers,
Shreya

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?

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

Change in Rejection flag for purchase orders (PO) - Output determination

Similar Messages

Maybe you are looking for