Overall Purchase Requisition
Dear Gurus
I am facing the problem of overall purchase requisition.
I have GFWRT - Total Purchase Requisition Value as a characteristic in Class ZPR_Release.
Now I am attaching this ZPR_Release with PR Release Group.
Now if I use this class in PR Group with overall Requisition Option Either in document type or in Purchase Requisition Group state, it is not working however when I remove the check of overall Req, it is working fine.
Can you please tell me what is the issue and what configuration I am missing
Regards
Sajid
Hi Sajid,
Few things to check:
1. Check the Class Characterisitc definition in CT04 and make sure the field GFWRT is mapped from the Communication Structure (table) CEBAN.
2. Check if the Overall Rel indicator is set for the PR Doc type definition in addition to the Rel Group settings
Set your Rel Strategy parameters in IMG andgo to ME54N and you should see the Release Strategy tab at the PR HEADER (Not at item detail section this time)
Let me know if this was helpful
Similar Messages
-
Overall Purchase requisition Release strategy : Changed after Rejected
Hi All,
I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
Problem I have is when PR is rejected .
When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point.
ME52 changes for PR is not trigerring any event which can trigger the WF.
Is there any way we can trigger Workflow in this scenerio.
Please suggest.Hi Subhashini,
This all depend on release strategy. release should reset completely on tha change.
For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
Sanjeev -
Overall purchase requisition's Workflow : mechanism of release code
Hi all,
i need to implement Overall purchase requisition standard workflow ; i need to have 2 actors for process's validation, so i set release code like this :
01 - ACTOR1
02 - ACTOR2
The workflow is launched, the ACTOR1 received a work item in his workplace, whe he execute the work item, the transaction ME54N is launched. Well. But the ACTOR1 can a decision for him but also for ACTOR2, why ? the process is not good for me. If ACTOR1 has taken a decision the workflow of release code 01 is finished. An other workflow is launched for release code 02, when the ACTOR2 go to the transaction ME54N he can take a decision for his relase code but he can also cancel the previous decision of ACTOR1, it's not good for me, can you explain to me ?
Thanks for help.
Cheers.Interesting solution using the user-exit.
I just finished modifying the delivered overall purch req approval WF. I needed to add a few fields for reporting so I created virtual attributes via delagation on BUS2105. I created approval and initiator agent attributes and email addresses. It works fine and I don't have maintain any further code other than what is in my business object which I can use again and again.
Many roads on the way to Rome -
Regarding overall purchase requisition release strategy
Hi,
For following combination PR release strategy is not working.
1.Total value of requisition
2.Purchasing Organization
3.Name of Requisitioner/Requeste
But when we take any one of them it is working. But when I tried to put together, these field system is not picking any release strategy.
What would be the reason? is there any inter connection between these fields?
Regards,Dear Aj,
Chek is theare any other release strategy in the syestem wth mentioned chraterstic,
also chek all chraterstic are ticked in the release strategy?
Some time syestem is not able to find the unique release strategy,
Please let me know -
Reg: Workflow for Overall Purchase Requisition Release
Hi Experts,
I have got a requirement in Overall or Header level PR release.
My question is,
for Header Level release,
I am using BUS2105 and what are the event I need to maintain,
so that my workflow get trigger.
Regards,
ShriraamHello ShriRam,
You have to use RELEASESTEPCREATED event if release steps are configured.
If no release steps are configured,you can use CREATED event.In such case, you have to implement a BAdI named ME_REQ_POSTED.
In either case, you have to use the change document BANF in the transaction code SWEC.
Regards,
S.Suresh -
Work flow for Purchase requisition
HI EXPERTS,
I am new for MM workflow, my client asked me to overall purchase requisition approval through work flow,i did configuration like
BUS 2105 -OBJ TYPE
WS20000077-RECIVER TYPE
RELEASESTEPCREATED-EVENT TYPE
AND ASSIGN AGENT ALSO.....
its working fine,and i get messages but my problem is i didnt release pr from inbox,
again i used me 54n for release .is there any chance to release pr from in box,,,
and also how to change time in time stamp column,i am getting wrong time please help me...
Thanks in advance
Thanks,
sivaYou need to verify that there is a teminating event. A terminating event works so that if you perform the action outside of the workflow inbox, the linked work item is "logically deleted" from the user inbox.
-
Ability to Change Overall limit in Purchase Requisition after PO creation.
Hi,
I have created a Service Purchase Requisition and released it.Then, I created a Service Purchase Order with reference to the above created Purchase Requisition and released and saved.
Now, when I go to the Purchase Requisition after creating a Purchase Order, I want to change the values for the Overall Limit and the Expected Value but they are greyed out.
But what I have noticed is that if I create a Standard Purchase Requisition and release it and then create a standard Purchase Order with reference to the standard PR and release it and save it, I am able to edit the values even after the PO has been created.
Any help is appreciated.
Thanks and Regards,
Puneet Jhari.Hi ,
I need to change the Accoun assignment category in back end not in fore ground.
Is there any EXIT or BADI available for the same.
Thanks,
Ranjit -
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 -
Can't use Overall Release for Purchase Requisitions
I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
This procedure is applicable only for Purchase Requisitions.
Here PR is released Item by Item only.
Release Procedure with classification
This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
Item by Item and Header level releases can be configured
For PR - both item by item and Header level release can be configured
For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
1) Total value of PR more than Rs 50,000
create characteristic as "Release_PR_total_value" in transaction code CT04.
Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
Tab -values key in > 50000 INR
Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
Tab - Restrictions - class type - 032 - Release strategy
2) Plant
Create characteristic "Release_PR_plant" in transaction code CT04.
Tab - Basic data - Data type - CHAR; Number of chars - 4
Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
Tab - Additional data - Table name CEBAN and Field Name is WERKS.
3) Purchaisng Group
Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
Tab - Basic data - Data Type - char, Number of chars eg. 3
Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user - Level - Release code
PR creator - clerk or Business user -
Approver - Supervisor - R1
Approver - Project Lead - R2
Approver - Asst. Manager - R3
Approver - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil -
Overall release strategy in purchase requisition
hi,
how do i configure overall release in case of purchase requisition. i have done item wise release in PR. but in case of overall release what field I should take in characteristics? is their required two seperate classes for item and overall release? i've allready chosen the field BSART and GSWRT for item wise release,
plz help me in details
regards
AniruddhaHi
For PRs, there are two types of release procedures available
With classification
With this we can release the PRs both items wise and in their entirety
Without classification
With this we can release only at item level
When you create the Release Group under the release procedure with classification
you check the box " ov Rel P Req (Overall release of purchase requisitions
This Determines that the items in a purchase requisition are all released at
the same time (rather than individually).
This should help to relsove your problem.
Regards
Vikrant -
Overall release of purchase requisitions - pr document type
hi,
what is the importance of the indicator Overall release of purchase requisitions while defining the PR document type.
Overall release of purchase requisitions
Determines that the items in a purchase requisition are all released at the same time (rather than individually).Hi Manipal,
overall release makes the release of all the items in the document.
u can also release itemwise in PR only and in all other external documents overall release is only possible
hope it wud have answered ur question.
Reward if useful
Shawn -
User Exit/BADI for Purchase Order and Purchase Requisitions
HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun BahalFor Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Regards,
Anirban -
Custom Event for Purchase Requisition Create, Change & Delete
Hello Experts,
I want to create a custom event which triggers on Purchase Requisition Create, SAP provide's standard event's for purchase requisition release but not for create.
What are all the steps and how to create a new event.
Thanks in Adavance,
Sandhya.Hi Sandhya,
may i know the reason why you are trying to create custom methods.
You have business object BUS2009(for PR line item wise release) and BUS2105(for PR overall release).
Both those business object have events RELEASESTEPCREATED (for PR creation) and SIGNIFICANTLYCHANGED(For PR change).
Even then if you want to create custom events, create a subtype of the standard business object, then click on events, and then select create. Now create your Z-events, say ZCREATED (For creation), ZCHANGED (for changed) and ZDELETED (for deleted). Now select each event, click on edit -> Change release status -> object type component -> to be implemented. Follow the same for all the events. Then select each event, click on edit -> Change release status -> object type component -> to be released.
Now click on your custom object, click on edit -> Change release status -> object type component -> to be implemented.Then click on your custom object, click on edit -> Change release status -> object type component -> to be released.
After this in SWEC tcode, click on new entries. Select change document object as BANF, business object as say ZBUS2105 and event as ZCREATED. make sure radio button on create is checked.
Similary create entries for ZCHANGED event and ZDELETED.
Select on change and on delete radio button for event ZCHANGED and ZDELETED event respectively.
let me know if you have any queries.
Regards,
Raj -
Purchase Requisition workflow escalation
Hi All,
I need help with purchase requisition workflow escalation. The workflow for the requisition escalate to the next level if not approved within 24 hours.So i dont want the workflow to escalate on weekend.
I want to know what can i do.
Tx RosiHi
For your Requirment :
"the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release."
Please follow the below steps.in copy of WS20000077.
1.For taskTS20000159:Overall release of requisition , go to
Latest END tab: put ACtion as :Modeled , Refer.date/time:Workitem creation , below time : choses: DAY, and on left add 2.
Outcome :Deadline Montoring.
2.Then come to OUTcomes tab of the same task: see there are 3 lines 1.Step executed, 2.Latest end:Deadline Montoring, 3.Processing obsolete:Processing obsolete ,, all are ACTIVE or not , if not, Activate .then all should be Green.
4.next in the OUtcome :Deadline Montoring , use a process control step. to Set missed workitem to obsolete, in Function: chose : set Work item to Obsolute. and Workflow Step : chose then step no for the above task(TS20000159:Overall release of requisition).
5.In "Processing obsolete" path, again call the same task TS20000159. in different activity . and see to the agent assignment.
I think this will slove your problem.
How it works:
1st the PR is send in a WI to the perticular agent by the 1st activity . if the agent do not execute for 2 days. then that WI will set to obsolute . and process flow to" Processing obsolete" path, then agian PR is send to the next agent using the same task but activity created in step 5.
thanks
Kakoli. -
Perform check after release step of purchasing requisition
Hi,
does anybody have a suggestion where to place best some logic which needs to be performed after a release step is performed successfully.
background: we use different types of Purchase requisitions, while each one is assigned to a static release strategy. I like to change it in more dynamic way by adding certain logic after a release step is performed.
example: if preceeding release step was 10 and purchase requisition is of type x then check purchase value and account assignment in order to process the current stepo automatically.
Currently the logic runs during a nightly job, but I would like to add it immediately after a release has been performed. I would imagin something like user exit, BusinessAddIn, or an event which I can use assign the job.
Can anybody suggest something?
Thanks in advance
Best regards
Torsten
Edited by: Torsten Hübsch on Apr 29, 2011 10:36 PMHi,
Enhancement M06B0005 is relevant for PR in case of overall release
Check on trx SMOD :
Enhancement M06B0005
Short text Changes to comm. structure for overall release of requisistion
--> Function module Short Text
EXIT_SAPLEBND_004 Changes to Communication Structure for Over.
Enhancement M06B0002 is for item-release
Short text Changes to comm. structure for purchase requisition release
-->
Function module
EXIT_SAPLEBND_001
BR
Nadia Orlandi
Maybe you are looking for
-
HT1420 how can i download an app on a new phone that was downloaded with the same apple id?
I mistakenly tried to use the same apple id to set up two phones and two iclouds. After realiing this would not work-I created a new apple id for mine, but it is not allowing me to download the same apps I purchased previously with the other phone. a
-
My Ipod Touch is not very well!
Hello, When I plug my Ipod in to my computer you can hear the beep that says the computer has seen the connection, yet it cannot be seen in My Computer. When the Itunes window comes up, there is a box with this message in it: "Itunes could not connec
-
How to change File Kind (not "how to assign an application to open a file?)
I build the toc.ncx file (part of the ePub setup) automatically, based on user input and source file content. It's fine, except that the file Kind (as shown in Finder Preview, for example) is Plain Text. The Kind should be Unix Executable File (the a
-
How can I restore my playlists?
My computer crashed an I lost all of my music. I managed to transfer the music from my ipod back to my computer by using it as a hard drive but I don't know how to transfer the playlists. I have tried folling this link as advised by Otto42: http://ot
-
Report in Organisation Management
Hi, I want to run a report based on company code and get the employee list to know there manager. Help me if there is any report in Organisation Management. Thanks, Padmaja