Release strategy in credit management

Dear All,
My client, wants to configure credit management in such way as
For some say Rs 20000/- debit, some X shd release the blocked delivery document
and for say rs Rs 50000/- debit, some X and Y shd release the blocked delivery document
I hope I am able to put my query in right perspective.
Kindly advice
Shailesh

Shailesh,
This one is very much possible.
You have to take help from your basis person for releasing these docs through vkm3, vkm4, vkm5.
With the help of BASIS you can restrict release strategy as per herarcy...
You will have to use some logic in Authorisation profile/Role with the help of BASIS..
AWARD PONIS IF U FINDS THIS AS USEFUL....
Regds
MM

Similar Messages

Release Strategy for Credit Note un the QM Module

Good SAP Guru's,
I have a very important question for you:
Is it possible within in the QM module (Transaction QM12) to implement a Release Strategy based on the value of the credit note to be created.
This should work on the same lines as the Purchase Order Release strategy.
Any guide lines and/or assistance will be gratefully appreciated.
Kind regards,
Leslie

Dear Leslie
We had done a similar kind of development in notification, not for credit memo though , but certainly can be incorporated in this case.We had done this for approving Short shipment and devaitions. If there has to be short shipment to be sent to a customer a notification will be trigered to manager and if he approves it will go for higher approval.
Please find my suggestion for this development
1) Make 3 task codes. for eg Task 1 for credit note is for less than u20AC500.00 . Task 2one for more than 501 and Task 3other one for more than 2001.
2) According the need of the credit notes to be created let the user assign the task and release it.
3) For task no 2 and task No3 a workflow triggers to the corresponding roles Sales manager & General Manager. ( please note that notifications are workflow freindly and standard workflows are available for the same)
4) if Manager wants to approve he can make the Task Complete. ( Notification tasks have 4 stages, outstanding, release, complete, Succussful)
5) Based on the status of the task you can make use of the action box in notification for creating the credit memo.
6) The credit memo creation will have to be developed. You will have to get ABAP support for this. They can either do it through user exit, or call transaction , and incorporate the same in the Action box of notification. (QQMA0001: User Subscreen for Notification Header, QQMA0014 Checks before saving notification )
please let me know your apprehensions
Regards
gajesh

Verison Management with PO release strategy - CEKKO-REVNO

Hello,
I'm a bit stuck... I'm trying to do a PO release strategy using version management, were the PO goes through a release strategy if the PO gets changed (not the intial PO creation).. So once the field RENVO is greater then 0, it should go through R.S.
I've read to create a characterstic CEKKO-REVNO and then assign it as a valuet <0... I intital;y created it with a NUM Data type, but the ABAP dictonary overides it with a CHAR instead... So I read to mark the value as a default value (<0)
However, after I add it to my class, I go to the define release strategy - classifcation section (to add the value <0) I'm getting a value inconsistency check.
How do i setup this characterstic so I can use it in release strategy?

Based on adding 00000000 the release strategy will work when its version 0 (intial). However, I'm trying to have it so it goes through a release strategy when the version is 1 or greater...
It seems like I cant get the strategy to work for more then one version... I can get it to work for version 0 but no others, or version 1 and no others etc...
I need to have it some it works for anything greater then zero, in which i tried <0000000 and even >000000
I also tried adding 000001, 000002, 0000003, 0000004 etc.. An although the release strategy tab is still applying, it will NOT result to a blocked status...
I cant get this to work... How should the characterstic value look to get this requirement?
Edited by: farmerj3 on Feb 20, 2012 3:16 PM
Edited by: farmerj3 on Feb 20, 2012 3:43 PM

Workflow for PR Release Strategy

Hi Expert,
   Is there a way the scenario given below will be possible to achieve..
   All the needed config for the PR release strategy has been define... (release code, group,release strategy,class & characteristic)
Parameter : Doc Type,
                  Amount
                  Acct Assignment Cat ( K,A,C)
                  Cost Center
                   Sales Order
The challenge is that when the given
               Doc Type - NB
               Amount - >0
               Acct Assignment Cat = C
               Cost Center - Empty
               Sales Order - 9999
The PR will be subject for release strategy of Project Manager ( Release Code :PM)
The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
She

Hi,
Thanks..but i have completed all the setting in PR release strategy .. -
Am looking for alternative/ ways that i can incorporate the partner function from SO using the sales order
as the link from the PR (charge to sales order) to trigger where the notification will flow through...
This is more i think in the workflow or userexit or abap, but i took the libertly of posting it here perhaps some of the member had this requirement before and how it was accomplished..

Release strategy should revert

hi
in PO we r using only release strategy not version management .
our scenario is like this , once a PO has released and if any body tried to do any change in PO after that , then those release strategy should revert to unreleased status.
guide us where to do right configuration .
what currently happening is , if in changing mode we are giving Quantity more then previous it is reverting release strategy other wise not .
regards
sachin sharma

Sachin,
As SAP standard, release strategy will be reset if:
- the changeablity of relesae indicator set to '4' incase of PR and '4' or '6' in case of another purchasing doc (PO, RFQ, contract)
-the document stii subject to previous release strategy
-the new TOTAL NET ORDER VALUE is higher then the old one
For release strategy reset in PO i suggest to use user exit.
Reward if useful

Re: PR Release Strategy with workflow

Hi Expert,
   Is there a way the scenario given below will be possible to achieve..
   All the needed config for the PR release strategy has been define... (release code, group,release strategy,class & characteristic)
Parameter : Doc Type,
                  Amount
                  Acct Assignment Cat ( K,A,C)
                  Cost Center
                   Sales Order
The challenge is that when the given
               Doc Type - NB
               Amount - >0
               Acct Assignment Cat = C
               Cost Center - Empty
               Sales Order - 9999
The PR will be subject for release strategy of Project Manager ( Release Code :PM)
The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
She

hi
i think u need workflow for release strategy
Steps involved are :
1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
3) Go to OOCU > here under MM, go to MM-PUR,
4) Click on "activate event linking"
5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
and Save.
6) Click on "Assign agents" and proceed all above steps.
BUS2012 is the relevant business object and Releasestep created is the event for the same.
7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
Test the same by creating a PO and check the SBWP for SAP Mail of respective Users
take help of ur BASIS person
hope it clears
regards
kunal

Use of step release in credit management?

Hi,
Is it possible to use step by step release or release strategy like the one in Purchase Orders to release the blocked sales orders in VKM1/VKM3?
Credit check can be either static or dynamic,
Blocked Orders should go to persons as per the amount to be released in Delegation of Authority.
what functioanlity in credit management can be used to achieve this.
Details of the configuration/step by step advise will be appreciated.
Helpfull answers will be rewarded.
Thanks and Regards

This can be achieved by giving the authorisations to the relevant transactions to the users with different authorisation levels.
Technically in credit management you can assign the creation to one person and change to another person.
But if you want authorisation based on levels say w.r.t amount then you need to do the organisational mapping of the people first and then create a workflow situation. What this will do is based on the different criteria you set it will seek the receiver of the message and download the message in the inbox of the person mapped who will then be able to process it.
For this you need to define workflow containers with receivers and is part of the workflow management.
IN SD plain its not possible but even
if workflow is not execute you could perhaps write an user exit where the system will first check the authorisation level of the user and see if the condition set is fulfilled and allow the person to process the transaction. This way we ca fulfil your requirement.
regds
Jude

List of released sales orders which were blocked during credit management

If sales order is blocked during credit management, then it is released by Authorised person using VKM3 Tcode. Further if we want to see list of released documents, VKM2 shows the same. However VKM2 does not shows the released documents once that are billed (using VF01). Suppose post billing one wants to see how many orders were released during specific period, how it can be seen. Is there any transaction code to see such records.
Vijay

You can use V.23 to view the report. The report will show you what sales order is ready for release for billing.

Credit Management: Use of release button in VKM2

3)what is the use of release button in VKM2. where does it releases?
Notes: If Credit Management is activated at Sales Order level and the credit block is removed through VKM1,VKM3 or VKM4, we can see the in VKM2 transaction code. But in VKM2 transaction code, we have release option .
What is the purpose of this options. Please assist me regarding the VKM2 transaction code.

The release button in VKM2 will have no affect on the document if it has already been released. I guess that if you release the document again the release date would be updated but nothing more.
I hope this helps.
Gerard

Credit Management: VKM4 (Release SD Documents)

Hi,
I have implemented Dynamic Credit Management at Delivery Level (02: Credit Group for Delivery). System is behaving also fine and is not allowing to save the delivery as soon as the credit limit of the customer gets increased.
But when I am trying to Release the sales order using Tx Code VKM4 (as an approval process), system is releasing the sales order in VKM4, but still at the time of delivery creation after releasing the sales order, it is again not allowing to save the delivery, saying that Dynamic Credit Check has been exceeded.
Can anyone help?
Regards,
Vikas

Hi Vikas,
What is the value for the status of the documents (Sales order and delivery). You can check it in SE16N for table VBUK, check this fields before and after run VKM4. ¿Are you using a userexit for the credit check? (flags user1 ot user3 in cheks in OVA8)
Field              Element                                                                         Name
CMPSA     CMPSA     CHAR     1     0     Status of static credit limit check
CMPSB     CMPSB     CHAR     1     0     Status of dynamic credit limit check in the credit horizon
CMPSC     CMPSC     CHAR     1     0     Status of credit check against maximum document value
CMPSD     CMPSD     CHAR     1     0     Status of credit check against terms of payment
CMPSE     CMPSE     CHAR     1     0     Status of credit check against customer review date
CMPSF     CMPSF     CHAR     1     0     Status of credit check against open items due
CMPSG     CMPSG     CHAR     1     0     Status of credit check against oldest open items
CMPSH     CMPSH     CHAR     1     0     Status of credit check against highest dunning level
CMPSI     CMPSI     CHAR     1     0     Status of credit check against financial document
CMPSJ     CMPSJ     CHAR     1     0     Status of credit check against export credit insurance
CMPSK     CMPSK     CHAR     1     0     Status of credit check against payment card authorization
CMPSL     CMPSL     CHAR     1     0     Status of credit check of reserves 4
CMPS0     CMPS0     CHAR     1     0     Status of credit check for customer reserve 1
CMPS1     CMPS1     CHAR     1     0     Status of credit check for customer reserve 2
CMPS2     CMPS2     CHAR     1     0     Status of credit check for customer reserve 3
CMGST     CMGST     CHAR     1     0     Overall status of credit checks
Regards,
Eduardo
Edited by: Eduardo Hinojosa on Sep 24, 2009 9:35 AM
Edited by: Eduardo Hinojosa on Sep 24, 2009 9:37 AM

Credit Management - In delivery process released document blocked

Hello SD Experts,
This is regarding credit management. we have configured Delivery level credit check.
As per the settings System block the delivery and FI credit representative release the blocked delivery documents.
Logistics processing the delivery , Picking and Packing with out problem.
While processing the shipping activity with combined delivery VT01n - when checking Shipment started tab its automatically going back to credit block.
I have configured in the Risk Category under Released documents are still unchecked as
Deviation -- Blank
Number of Days as 15
My requirement is once released from delivery no need to do credit check again - with any deivation and Number of days limit also
Please help me to resolve this issue.
Thanks in Advance
Jaffar

Hi Jaffar,
As per your explanation this is happening because of Number of Days as 15
This specifies the number of days after which a changed document must be re-checked for credit.
This function is used for checking documents that have already been released by a credit representative, but that have
subsequently been changed. The system does NOT carry out another credit check if the following conditions are met:
The value of the changed order is not greater than the value already approved for credit (inclusive of the deviation factor),
AND
The current date is not greater than the original release date plus the number of days specified here.
As per this there might be any changes in released document or changes in delivery dates,due to this reason system
blocking it again,try to reduce the number of days from 15 to 5 or as per your convenience and check.
Regards
Ram
Edited by: Lakshmipathi on Dec 13, 2011 6:55 PM
Instead of copy pasting from standard, it would have been better had you advised the member to press F1 against that field (Number of days). Please dont ever try to copy paste from other source which is strictly prohibited

In ME38 can we add Version Management , Release Strategy

Hi,
Is there any way to add Version Management and Release strategy in ME38.
Thanks & Regards
Sudhansu

Hello ,
Please check the settings
Here Activate (Tick) for LPA .
please check and revert back.

Credit Management doesn't release hold from order (11i)

Hi guys...
In some cases Credit Management doesn't release the hold from order automatically.
I'm debugging CM Workflow and I didn't find anything.
So in these cases we need to force it by executing a custom concurrent.
I've found some open bugs at metalink but I'd like to know the reason for that.
Anybody knows?
Tks
Best Regards,

I have a very similar problem:
I wrote an application that uses SAP DI and writes many dozents of draft documents. It doesn´t make a difference if I set
objDoc = objCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDrafts) for each document or not: every document leeches round about 2-4 MB. That is, in case of an import of 100 documents, up to 400 MB are used.
Isn´t there a possibility to minimize the volume of leeched memory?
Info: I´m using DI and UI, but I am filtering ANY Events from the UI (just need it for singel-sign on).
regards,
Marian

Release strategy in SD + workflow

hi SD Experts,
it is possible to customiz "Release Strategy " in SD as for the case of MM (PR, PO)??
if it is possible, how can we customiz "Release Strategy" in sales Order or Outbound Delivery, ...? give the IMG path and the necessery custo to do please.
NB: if you have any doc on release strategy in SD + Workflow in SD, please it to me on: [email protected]
thank's in advance
Cordialy
Said

Hi
I dont think there release strategy for sales orders.
You may use credit management functionality or delivery block.. set it in the item level or header level for the order, provide authorization to one person who can remove block.
or Use TCode BS02 and create a status profile, maintain statuses and assign the authorisation code to the release status. You can get into details of each status and set the actions permitted for the status.
regards
Srinivas

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Release strategy in credit management

Similar Messages

Maybe you are looking for