Purchase Requisition Overall Release problem with several CostCenter

Hello Gurus!!
I need your comments!!!
I define the Purchase requisition as Overall Release, and woks !! but I have a Issue.
I have an entry in the CL24N txn as follow:
AccAssgCat = K
Plant              = CC01
CostCenters = 10001
                        10002
                        10003
totalAmt        = 1USD to 1000US
So when I create my purchase requisition with only 1 Cost Center the release strategy is called and PR can be released.
But When I create the purchase requisition with CC 10001 and 10003, the requisition is not subjet to release!!! (note TotalAmt = 15usd)
I assume that as both are into the release strategy the system will take both CC and ask for release!!
What I can do to fix this situation??

Dear Marco Antonio,
I have never faced your issue, but have an idea of what you can do.
Activate Enhancement M06B0005 EXIT_SAPLEBND_004
Then in the program zxm06u31 put the following code line:
e_ceban = i_ceban.
and also a breakpoint so that it stops automatically upon PR verification or saving.
Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
Well, tell me what happens
Best Regards,
Sebastián Ligueros

Similar Messages

Purchase Requisition Overall release amount

Hi,
I am working on PR overall release amount workflow.
How can i find the overall release amount in the tables of PR while entering into the workflow.
Depending on this amount we need to further proceed for approval process.
Regards,
Gopinath Addepalli.

Dear Marco Antonio,
I have never faced your issue, but have an idea of what you can do.
Activate Enhancement M06B0005 EXIT_SAPLEBND_004
Then in the program zxm06u31 put the following code line:
e_ceban = i_ceban.
and also a breakpoint so that it stops automatically upon PR verification or saving.
Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
Well, tell me what happens
Best Regards,
Sebastián Ligueros

Purchase Requisition, overall release

Hi All,
I am using the overall release for my release groups. The releasing strategy depends on the cost center.
The releasing is workling fine so far, after I created a PR, the release tab appears in the header. BUT if I enter several items in one PR with different cost centers, the release tab does not appear. This also happens, if I enter 2 items with different cost centers in the PR and both of them are assigned to the same release strategy.
Are there any configuration in SAP to prevent this or do I have to use the itemwise release for that?
Thank you!

Use userexit
Enhancement : M06B0005
Component   : EXIT_SAPLEBND_004
CR : RDAK903063 SPOREDDY 04/05/07 changes to pick the release
              strategy if all the cost centers are same for all
                line items. Since the user Exit is activated the
                program is forcing the data to go through import and*
             field I_CEBAN-KOSTL is not blank the user exit is
                filling blank values to E_CEBAN during export.

Purchase Requistion : Overall Release Problem

Hi everybody,
Have a peculiar problem where Item Level release seems to be working fine. And the first time we want to use release at header level and its not working.
The OverReqRel (overall requisition release) is 'checked' [at release group level].
There is just one class, one characteristic within that class (document type).
There is just one group, release code, release indicator and release strategy.
The classification has 'NB' as the document type to be controlled.
The simulation works fine.
The 'Check Release Strategies' shows 'all green' with no errors.
But when we create a PR (txn ME51N) for document type NB, this procedure does not kick in (hence i dont see a new tab at the header level asking for a release).
We have been using item wise release before and are testing the viability of release at header level.
FYI. This is a test system (sandbox) where we have NO configuration for release procedure. This is the first strategy that has been created for testing.
Any help in getting this to work is most welcome.

Hi,
For the document type NB, did you flaged as PR header level release.
Regards,
Ramakrishna

Problem with severe connection fail and slow inter...

Havin problem with several automatic disconnection, slow internet and cant get inside online bt repair centre coz its sayin - this no is not provided by bt business...
ADSL Line Status
Connection Information
Line state: Connected
Connection time: 2 days, 06:57:44
Downstream: 1.122 Mbps
Upstream: 80 Kbps
ADSL Settings
VPI/VCI: 0/38
Type: PPPoA
Modulation: G.992.5 Annex A
Latency type: Interleaved
Noise margin (Down/Up): 4.0 dB / 7.2 dB
Line attenuation (Down/Up): 65.0 dB / 34.6 dB
Output power (Down/Up): 19.1 dBm / 10.0 dBm
FEC Events (Down/Up): 9019906 / 503
CRC Events (Down/Up): 656 / 131
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
HEC Events (Down/Up): 5492 / 23
Error Seconds (Local/Remote): 62 / 33

as you are a business user you need to post on the business forum https://business.forums.bt.com/
this forum is for residential customer
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Purchase requisition still contains items with errors

DER SIR / MEDAM
PLEAE PROVIDE ANSWER
Purchase requisition still contains items with errors
Edited by: Csaba Szommer on May 1, 2011 6:56 PM

Hi
The error message ZPSMSG003 seams to be customized
Please check for User exit for material compnents COZF*

User exit/BADI for Purchase requisition through release of Process order

Hi ,
i need to add some text to the Pur Req.
The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
regards

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
Regards
Anji

Creating purchase Requisition and release Overview

Hello,
We have some User which have the authorization to create a purchase Requisition and also to release it by themselves.
We have to Monitor this cases and I' looking for a possibility to check this on a easy way.
I found the Report "Changedocu_read". There I can check several changes in the PR and see who released it. But there I can not see which User created the PR.
The table EBAN has the informations about the User who created the PR and if it had to be released and some more informations. But the informations who released the PR is missing.
I tryed a table-join of the tables EBAN and CDHDR. But it was not possible, because the PR Number (Filed "BANFN" in the EBAN) has not the same format as the number in the Filed "object value" in the table CDHDR.
Perhaps someone has an idea ?
Or there is an Standard Transaction which I did not found to have an overview of the PR and the releases
It would be enough to see following informations with one Join or Transaction:
-PR Number
-Creation Date
- Transaction code
-Change Date
-Release Status
-Released date
-Released by User
I have the same Topic also by purchase orders and the release of them.
Thank you in advance
Regards
Dirk

Thanks both for the quick reply.
@AKPT
The Transaction is nice and helpful to Display some informations. But similar results I also receive when I use the Programm : "changedoc_read". I also had the idea to join the informations of the 2 sources in Excel. For me this Workaround would be ok.
But unfortunately I' m looking for an simply way (for the Enduser). To get this informations mentioned above in one overview directly in SAP.
They have to use this check regularly, to Monitor if there were some wrong Releases.
If there is not such a way then we have to join it in Excel.
But if you have some other suggestions I'm happy to hear them.
Regards
Dirk

Purchase requisition create/release

Hi
I am creating purchase requisition. And i want to release this requisition.
But in my created purchase requisition there is no tab such as release strategy
And i want to keep my purchase requisition as blocked initially and later i want to release it. Can u please tell me what are the configuration or release procedure i've to do to make this happen.
I know purchase requisition can be released be me54n. But my created purchase requisition is not release relevant.
I hope u understood.
with regards
mandeep

Hi Mandeep,
For release strategy cstomising u need to go spro
Matl mgmt>Purchasing>Purchase requisition>Release procedure with classification
there u maintain, characteristics, class, create release strategy and maintain, release group, release code and indicator etc. Once u do all this then u will get the tab in PR
hope this helps
regards
Anand.c

Purchase requisition- Mat. description problem.

Hi Experts,
I am stuck with one problem regarding Purchase requisition material description. The scenario is as follows.
We have two types of PR creation. With or without material code.
Material description is set to display only. But if the user enters the material code and random description and then press Enter button then the system doesnt pick the description from MAKT and keep the random description and disabling it for input. As shown in below screen shot.
I want to restrict this, So I used the enhancement - MEREQ001 in CMOD and exit - EXIT_SAPLMEREQ_010 and INCLUDE ZXM02U12 , to compare the material description and change it to master data from table MAKT. But the problem here is the original PR data fetched in to the exit is not changing. I have written below code.
+++++++++++++++++++++++++++++++++++++++++++++
LOOP AT im_t_eban INTO l_s_eban.
IF l_s_eban-matnr <> ''.
        SELECT SINGLE maktx FROM makt INTO mde
          WHERE matnr = l_s_eban-matnr.
          IF mde <> l_s_eban-txz01 .
            MESSAGE w007(zm_msg) . " DISPLAY LIKE 'E'.
            l_s_eban-txz01 = mde.
              MODIFY im_t_eban FROM l_s_eban TRANSPORTING txz01. " THIS LINE IS GIVING SYNTAX ERROR THAT im_t_eban is not changeable
          ENDIF.
      ENDIF.
ENDLOOP.
++++++++++++++++++++++++++++++++++++++
So how to solve this problem??
Or is there any other way to restrict the user to change the material description ??
Thanks,
Vishal .

hello abaper,
have a look on this
Hi Gaurav, try this:
http://scn.sap.com/thread/3297154
FIELD-SYMBOLS: <T_EBAN> type mereq_t_eban.
FIELD-SYMBOLS: <im_t_eban> type mereq_t_eban.
DATA: wa_eban LIKE eban.
ASSIGN ('(SAPLMEREQ)LT_EBAN[]') to <T_EBAN> .   <-Uncommet this line
LOOP AT <im_t_eban> INTO wa_eban.
* => here you can change the value
   SELECT SINGLE matnr maktx into (mcode,mdesc)
         FROM makt
         WHERE matnr = wa_eban-matnr.
     if sy-subrc = 0 .
     move mdesc to wa_eban-txz01.
   MODIFY <T_EBAN> from wa_eban TRANSPORTING txz01.   <-Change the field-symbol for the one that is referencing the standard table
     ENDIF.
ENDLOOP.

Purchase requisition must be create with material codes only

Hi gays,
Can u solve my problem.
We are having "3 " document types to create purchase requisition.
3 types are using different depts.
I need to restrict the 1 document type with material code only they should raise the purchase requisition.
other 2 types can raise the purchase requisition with or with out material code.
Please explain how to restrict.

First check the field selection key assigned for the Document type at
Spro > MM > Purchasing > PR > Define document types..
Then Go to
Spro > MM > Purchasing > PR > Define Screen lay out, here Select the above field selection key & copy it as and make the
Description field as Display..
Again go to Spro > MM > Purchasing > PR > Define document types..
and assign the field selection key for the Document type for which you want the Description field as Display..
Then Create PR & Check

PR overall release strategy (with shared PR document types)

We are asked to configure 'overall' PR release for some of the plants of our client.Now ,we know, this needs to be configured in two places in SPRO. One, in release group definition & two, document type (PR) definition. Our issue is that the doc types involved here is shared by some other plants as well who doesn't need 'overall' release. Is it possible to configure the requirement without disturbing the unwilling plants ?

Hi ,
The PR release strategy can be done at Item level also ,which has to be set that the PR has to be released at item level and after doing it ,all the item values can become characteristics values for the release strategy
The Plant can be taken as one of the characteristic.
The view CEBAN gives all the related views.
check the below LInk for Futher information on the same.
http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
hope so it helps
Regards
Anjanna.

I purchased CS6 and had problems with the Adobe Acrobat Pro so i uninstalled and now need to reinstall but serial number wont work. How can i reinstall ONLY Adobe Acrobat Pro since its included in CS6?

I purchased Design Standard CS6 the entire package. I downloaded and installed but I was continually having problems with Adobe Acrobat Pro. I tried updating to the newest version but it only made the problems worse (acrobat was super slow and constantly not responding). So i decided to try to uninstall and then reinstall the program. Well I uninstalled, and then attempted to reinstall ONLY the adobe acrobat pro but it says my serial number (which is for design standard) will not work. Since Acrobat Pro is included in the suite, i thought this wouldnt be a problem. Is there anyway to get around this without uninstalling the entire design standard and reinstalling everything? I only need to reinstall acrobat pro.

You need to reinstall Acrobat the the Creative Suite, you cannot download it is a separate application and install it that way because it will be looking for a serial number relative to being a singly purchased application.

Purchase Requisitions stuck in CIf with message 181

Hi All,
We have purchase requisitions created in APO on transportation lanes based on external procurement relationships. We have noticed that the requisitions are created in ECC but get stuck on their way back to APO. They appear in /sapapo/ccr with message 181.
Any ideas where we could be going wrong?
Regards,
Zeeshan.

you need to push this Orders in APO through CCR .
some times schedule line are not created/updated in APO so we need to push it through CCR report.
On CCR report screen select all the PO and click on arrow button send to APO .
Than click on iteration icon .
this will push all PO to APO and will not appear in next CCR run.
If it didn't help please check OSS note :
Note 1152934 - DELTAREPORT:confirmation-error 181 for after return delivery
Note 1131469 - DELTAREPORT: unjustified error 181/183 for confirmation

Do the purchase order can be created with several purchasing groups?

Hello gúrus,
I need your help again a.s.a.p. please!
We are implementing SAP R/3 ECC 600 and we have SRM too.
In the SRM is possible to create a purchase order with several purchasing groups, but, in MM we cannot because of the purchasing groups is the the header level.
Somebody expert from SAP told to the client that its possible to create a Purchase order in MM with several purchasing groups..
Is it possible? or, where I can find information from SAP that said that its not possible?
Could you help me please?
Regards,
Sandra Palomo

How can I create a PO with different purchasing groups to the same PO?
Could you give me a detail?
Regards,
Sandra Palomo

Purchase Requisition Overall Release problem with several CostCenter

Similar Messages

Maybe you are looking for