How restrict the release procedure tab in ME21N
Hi,
We have the Condition tab for free goods Iin PO.
Now, we want to implement release procedure in PO, and also restrict the release procedure for free goods in the same based on the combination of document type (EKKO-BSART) and free goods (USMON)field. Please provide the solution.
Regards,
Mars.
Hi
Try using the exit M06E0004.
Regards
Shiva
Similar Messages
-
How to configure release procedure for rate contracts release
Dear all,
How to configure release procedure for rate contract following are the requirements
they are two release codes c1 & c2 <=100000,>=100000
if c1 is not there c2 has to be approved
Change in the value of the rate contract contract
Change in the validity of the rate contract
Addition of deletion of line items
While using a non u2013 released rate contract in the PO an error message should shoot out.
Also the logic should be changed while using the rate contract in the PO.
The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
It should be possible to refer existing valid rate contracts in purchase orders.
Regards,
bhaskarHi,
In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
class in standard is the same FRG_EKKO, you can use the same for contract.
To distinguish if it's a contract or PO, EKKO-BSART can be used.
For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
You can restrict the document type to set up the release strategy for only contract.
Of cause, you can also create your own release class Z* for contract copying standard
one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
OLME:
-> contract
->Release Procedure for Contracts
->Define Release Procedure for Contracts
->Release Groups
If you have already created the PO release class.
Assign a new chracteristic of Document Category -BSTYP
Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES -
How to extend release procedure
Dear Friends,
Now we extending all Materials to a newly created plants.I want to know how to make the same release procedure to the existing plant also??
Now in the newly created plant the release procedure is not working.
Can anybody help me...................Hi,
You need to ensure that the new plant is present in the classification system.
Please use CL24N to select the new plant, after adding the same in edit characteristics.
Also verify, by changing the plant to an old plant to see whether for the same document and other values, a release strategy is being called.
Please let me know if you need any more information.
Regards
Shailesh -
How to update Partner function tab in ME21N Transaction
Dear Guru's,
I have a requirement to call a selection screen in ME21N transaction which will show list of vendors available. the selected vendor in the selection screen should be updated with parnter function 'CR' in the Parnter function tab of ME21N Transaction and EKPA table also.
Thanks & Regards,
Sridhar R Perumalla.Hi,
Use the function module MM_UPDATE_PARTNERS for updation ....and wite the code in ME_PROCESS_PO_CUST badi in process_header method...
in PROCESS_HEADER method use GET_DATA to get the entered vendor number in PO.
Thanks,
Shailaja Ainala. -
Can I restrict the release of Preq by creator in customizing?
hello
as far as I know, restricting the release of preq in a way that the requisitioner cannot release it own preq, is only via roles. I have been told that there is a way to do that in customizing but cannot find it: has anyone ever encounter such a restriction in customizing? if yes, where?Hi,
You can easily restrict and control PR release process by having well designed user authorization matrix and release matrix. As per release u201CVALUESu201D, release matrix designed and based on authorization, control can be established for transaction codes.
Lets example: User 1 will create PR, user 2 will change PR and you have 3 codes for releasing PR like C1, C2, C3.Now you can allow(authorized to) user to do following transaction
Transaction Code----
> User
ME51N----
> user 1
ME52N----
> user 2
ME53N -
>(All users ie..user1.user2,user3,user4 &user5)
ME54N with release codeC1----
> user3
ME54N with release codeC2----
> user4
ME54N with release codeC3----
> user5
NOTE: For more details contact basis team and control all these by authorization object.
Regards,
Biju K -
Unable to restrict the Release of order when the Stocks are deficit.
Hi gurus,
i have a packing material for which the stocks are deficit when i checked in MMBE.
While releasing the order the material is picking the stock from some where and is not restricting the Release of order. The same case is working fine with other materials as well.i.e when there is a deficit of stock then the release is Rejecting for all the materials except for this packing material.
Thanks for your understanding.
Naveen.AHi,
Please check the below mentioned points
1.Material Master MRP View : (View 2 or 3, i dont remember) You had maintained the proper Checking Group (Say 02)
2. OPJJ: If you are using standard Checking Rule "PP" for the combination of the Checking Group and Checking Rule PP, make sure that scope is defined properly. Generally receipts from PR would be out of scope.
3. OPJK : Make sure "you had NOT checked "No Check" for Material Availability.
4.OPJK: The checking Rule is the right one (PP in Standard)
5. OPJK : For the order type you use, the Plant and business function 2combination check if you had set "3 - No release if Parts are missing" for the field "Release Material"
Thanks
Bala -
PO and PR - How to find the release procedure
How can I find the authorization strategy for Purchase Order for the Purchase Requisition. I also want to know that how these are connected where can I see these in which transaction code?
Thank you.For PR:
SPRO>Materials Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification>Release Strategies. Then select your line and see the details.
For PO:
SPRO>Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release Strategies
Then select your line and see the details. -
How to restrict the upload file size in me21n/me22n/me23n?
Hi Guru's,
I have a requirement to restrict the user from attaching a local file more than 20MB in Purchase Order.
In standard SAP system, the user can attach a file of any size in PO. How to restrict the size of the file?
I have no clue how to achieve this? Any kind of help would be great...
Thanks in Advance...
Regards,
SatyamHi Guru's,
The file size is now restricted in function GUI_UPLOAD. But this function module is used at many places. I want to restrict it only for Tcode: ME22n and ME23n.
I thought of restricting it by sy-tcode field but sy-tcode value is not passed to this function module in the run time.
Could anyone help me on this how to restrict it for the above mentioned tcodes??
Regards,
Satyam -
Workflow To restrict the release of Transport request
Hi Guys,
Can any one tell me is there any Standard workflow to restrict the User's to release the Transport Request?
Regards
Venkatesh.S
Edited by: venkatesh saravanaperumal on Jan 16, 2008 11:40 AMCheck this template
30000524
45301534
71000008
74500938
74500939
Thanks
Arghadip -
Help to modify the Release procedure without disturbing the existing class
Hi All,
We have a requirement to modify the existing workflow approval procedure for PR and PO to include a case, where the PO amount is less than certain value (say 100 EUR) and the material group is equal to certain value, then we need to include the approval levels L2 (defined for PR) and X2 (defined for PO).
Taking the case for PO`s, please note the following information,
Existing release Strategies & release Levels for PO are
51 Level X4
52 Level X4 + X3
53 Level X4 + X3 + X2
54 Level X4 + X3 + X2 +X1
Characteristics used
Total Net order Value
Purchasing organization
Order Type
Purchasing Group
Example : If the PO triggering a Release strategy 51 and if the conditions PO Value and Material Group satisfied then in addition to X4 system should send the PO Approval to X2 also. Similarly if the Po triggering the Release strategy 52 then in addition to X4 + X3, approval from X2 also required (provided if the condition satisfies).
Solutions tried
1) We can achieve the requirement by adding a dummy variable in the Characteristics and defining the new release strategy 55 with Level X4 + X2 and using the User Exit EXIT_SAPLEBND_002 .But we donu2019t want to touch the Characteristics and class because this is used by other companies also.
2) Also we can add a characteristic Material group with value equal to the required value and define 2 new release strategies 55 with Level X4 + X2 and 56 with Level X4+ X3 +X2.For all the other release strategies we can maintain the material group value as blank. Since the characteristics used by many companies we donu2019t want this option also.
Request your valuable suggestion to meet the above requirement, without disturbing the existing characteristics and Classes, would be highly appreciable.>
MadhanRaj S wrote:
But we cannot use those because these are used by other companies of the same organization.
>
> We need a solution other than these two options with out disturbing the existing charecteristics and class.
It looks to me like you need a new release strategy for the company that is different. This is a perfectly normal way to use release strategies and is exactly what they are designed for.
Cheers,
Mike -
How is the tax procedure determined on a transaction?
Hi !
We are using a bolt-on for US tax transactions and internal functionality for VAT.
Now, the US entity needs to sell from an EU plant under an EU VAT ID.
We crated and assigned a new pricing procedure in SD to pick up MWST conditions and created appropriate condition records to assign EU tax codes.
In SD, all goes well; the appropraite tax codes are assigned, rates used in calculations etc.
However, when we release to accounting. We get an error that "Tax Code XX is not assigned to Tax Procedure TAXUSX."
It was my understanding that the country of the shipping plant was the country that drives the Tax Procedure selection, so I would have expected the system to find the appropriate EU tax procedure etc. Why is the system finding the Tax Procedure for the United States?
Help!Hi,
In SD the country of the shipping plant is used for the tax procedure.
In FI the country of the company code is used for the tax procedure.
In cases where the countries are different ,you have to maintain the same tax code in both relevant procedures.
SD only transfers the tax code to accounting (not code + procedure) , so accounting looks for that tax code in TAXUSX.
Kind regards -
How restrict the export option in CrystalReport
There are many export format in crystal report when user click on export (save) button
1. Crystal Report
2. PDF
3. HTML 3.2 and HTML 4.0
4. Microsoft Excel (97-2003)
5. Microsoft Excel (97-2003) Data-only
6.Microsoft Word (97-2003)
...etc
I want keep only CrystalReport and PDF and remove the rest of the formats. Please help me in it?
Thanks,
DynaCrystalHi,
As discussed earlier, the only workaround possible is to export your reports using code. Thus, I am providing you the following sample code to export report to specific format (i.e. PDF in this case)
<%@ page import = "com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException" %>
<%@ page import="com.crystaldecisions.sdk.occa.infostore.IInfoStore"%>
<%@ page import="com.crystaldecisions.sdk.occa.infostore.IInfoObjects"%>
<%@ page import="com.crystaldecisions.sdk.occa.infostore.IInfoObject"%>
<%@ page import="com.crystaldecisions.sdk.framework.IEnterpriseSession"%>
<%@ page import="com.crystaldecisions.sdk.framework.CrystalEnterprise"%>
<%@ page import="com.crystaldecisions.sdk.framework.*"%>
<%@ page import="com.crystaldecisions.sdk.occa.report.application.*" %>
<%@ page import="com.crystaldecisions.sdk.occa.managedreports.*" %>
<%@ page import = "com.crystaldecisions.sdk.occa.report.exportoptions.ReportExportFormat" %>
<%@ page import = "java.io.ByteArrayInputStream" %>
<%@ page import="java.util.Locale" %>
<html>
<head>
<title>Export Report</title>
</head>
<%
// Set the logon information
String boUser = "Administrator";
String boPassword = "";
String boCmsName = "localhost";
String boAuthType = "secEnterprise";
String reportName = "Customer";
// Logon and obtain an Enterprise Session
IEnterpriseSession boEnterpriseSession = null;
boEnterpriseSession = CrystalEnterprise.getSessionMgr().logon( boUser, boPassword, boCmsName, boAuthType);
// Get the Report Application Factory service from Crystal Enterprise
IReportAppFactory rptAppFactory = (IReportAppFactory)boEnterpriseSession.getService("", "RASReportService");
// Get the InfoStore service from Crystal Enterprise
IInfoStore boInfoStore = (IInfoStore)boEnterpriseSession.getService("", "InfoStore");
// Retrieve the report by name from Crystal Enterprise
IInfoObjects boInfoObjects = boInfoStore.query("Select SI_ID From CI_INFOOBJECTS Where SI_NAME = '" + reportName + "'");
// Open the report into a Report Document object
ReportClientDocument rcd = rptAppFactory.openDocument((IInfoObject)boInfoObjects.get(0), 0, Locale.ENGLISH);
// WORKING WITH THE PRINT OUTPUT CONTROLLER
// Use the report documents PrintOutputController to export the report to a ByteArrayInputStream
ByteArrayInputStream byteIS = (ByteArrayInputStream) rcd.getPrintOutputController().export(ReportExportFormat.PDF);
// EXPORTING THE REPORT
// Create a byte[] (same size as the exported ByteArrayInputStream)
byte[] buf = new byte[2000 * 1024];
int nRead = 0;
// Set response headers to indicate pdf MIME type and inline file
response.reset();
response.setHeader("Content-disposition", "inline;filename=untitled.pdf");
response.setContentType("application/pdf");
// Send the Byte Array to the Client
while ((nRead = byteIS.read(buf)) != -1) {
response.getOutputStream().write(buf, 0, nRead);
// Flush the output stream
response.getOutputStream().flush();
// Close the output stream
response.getOutputStream().close();
%>
Regards,
Shreyans Surana -
Effect of payment terms on release procedure
Hi gurus,
Will their be any impact of payment terms on release procedure of purchase order?
As and when we change payment terms in a PO which is released earlier, the release procedure tab is getting disappeared
I hope my question is clear
Kindly reply soon
regards,
prasadHi Prasad Sathya
Be sure that Payment term in Po will not have any impact on release procedure. if u check the Table CEKKO throgh T code SE11 , there will not be any field for payment term. then how to create characteristic for the payment term.
and it is not logic to create Release procedure based on the Payment terms
friendly
Manickss
pl don't forget to reward if helpful -
How to set the Release Strategy without classification for PR
Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh1. Release codes
Create the release codes. For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
2. Release indicators
Define release indicators and branch to the detail screen. Here you
define whether fixed purchase requisitions may be changed by Materials
Planning, for example, and whether an RFQ or a purchase order may be
created from the requisition.
You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you
specify whether a requisition may be changed after the release
procedure has begun. You specify whether the strategy has to be
redetermined after changes, or whether the release procedure has to
start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For
example, previous releases are not cancelled if the value of the
requisition item after the change does not exceed plus 10% of its
original value.
Attention:
Be sure to create a release indicator (e.g. B for "blocked") that
serves as the starting point for subsequent indicators. Do not set the
indicators for release for the issue of RFQs and PO on the detail
screen for this indicator.
Also create a release indicator characterizing the released status.
Set the indicators for release for the issue of RFQs and PO on the
detail screen.
You can use sytem defined indicator in this case you dont have to do anything
3. Assignment of release indicators
Assign a release indicator in dependence on the status of the release.
Example:
You create a release strategy S1 consisting of two release codes 01
and 02. Release with 01 is a prerequisite for release with 02. If
release has been effected with 01, the requisition has been given the
"all clear" for the issue of RFQs.
You have created the release indicators B (blocked), 1 (cleared for
issue of RFQs) and 2 (cleared for RFQs and PO).
Now enter the following as assignment:
Strategy C1 C2 C3 ...
S1 B (blocked)
S1 X 1 (RFQ)
S1 X X 2 (RFQ/PO)
4. Release prerequisites
Define which release codes are involved in a release strategy. Specify
whether a code is set for a release status following release, and
whether one release status is a prerequisite for another (+).
Example:
Strategy Code C1 C2 C3 ...
S1 01 X
S1 02 + X
5. Determination of the release strategy
Determine the conditions under which each release strategy is
assigned. The criteria are account assignment category, material
group, plant, and value of the requisition item.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
<b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only. </b> -
Release Procedure in Indent/Purchase Order
I want to customise release strategy in indent and Purchase order in SAP. Kindly provide me steps to configure this. will apperitiate your efforts.
ManjitHi Manjit,
Release Procedure for Purchase Orders
In this section, you set up a release procedure for purchase orders (POs).
Requirements
If you want to use workflow to release POs, you must make the standard and basic settings for workflow (Basis -> Business Management -> SAP Business Workflow).
How do you set üp a release procedure for POs?
To set up the release procedure, you must make a series of settings in Customizing. This section provides you with an overview of the necessary activities.
You must perform the following steps:
1. Create characteristics and classes
For more on this topic, see Edit Characteristics and Edit Classes.
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3 . You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
Define organizational plan
For more on this topic, see Edit Organizational Plan.
Assign standard tasks and activate event-receiver linkage.
For more on this topic, see Perform Task- Specific Customizing.
1. Set up release procedure for RFQs
a) Create release group
b) Create release code
c) Create release indicator
d) Create release strategy
Note
You need only carry out the following step if you wish to link your release procedure to workflow.
e) Assign release code to a user
For more on this topic, see Define Release Procedure for POs.
2. Check release strategies
For more on this topic, see Check Release Strategies.
Further notes
For more information, refer to
· Implementation of a Release Procedure for Purchasing Documents
· Release of Purchasing Documents (SAP Library -> Basis -> Business Management (BC-BMT) -> SAP Business Workflow (BC-BMT-WFM) -> Reference documentation -> BC Workflow Scenarios in the Applications -> MM Materials Management: Workflow Scenarios)
Edit Characteristic (CT04)
In this step, you create characteristics for a release procedure for purchase orders (POs).
Classification characteristics are the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchasing document (e.g. purchase order or RFQ).
Example
Release condition for release strategy EA:
Characteristic Characteristic value
Total net value of PO Above $10,000
If the total value of a purchase order exceeds $10,000, release strategy EA is assigned to this PO.
Requirements
In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table , and choose "Display".
Note
If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
Activities
1. Create a characteristic for each field from communication structure CEKKO that is to be a criterion for your release strategy. You have a free choice of names for the characteristic.
2. Enter the table name and the field name on the tab page Additional data (for example, table CEKKO for field GNETW).
Note
o Do not select any of the indicators in the area Procedure for value assignment on the tab page Additional data. Only if none of these indicators is marked can you assign a value or value interval to the characteristic when defining your release strategy.
o When you create a characteristic for a currency-dependent field (e.g. GNETW), a box appears in which you must enter the currency for the relevant value. The system then converts the currency of the purchasing document into this currency.
3. Check the data for the chosen field on the tab page Basic data.
If you want to enter several values or a value interval for a characteristic, set the Multiple values indicator in the area Value assignment.
Note
Value intervals can only be specified for numerical values (e.g. an interval of $10,000 to $15,000 for the value of the purchase order.
4. Check the texts for the field on the tab page Descriptions.
5. You can maintain default values for a characteristic on the tab page Values.
If you maintain values here, these values will be displayed as input help under Create Procedure with Classification -> Release Strategy -> Classification . If you wish to use not only the input help but also other values, you must select the Additional values indicator.
Note
You can also maintain ' ' as a default value. For example, for account assignment: ' ' for stock material, 'k' for cost center, and 'a' for asset.
6. If you want to restrict the use of a characteristic to particular class types, specify the relevant class types on the tab page Restrictions. For example, class type 032 for the release strategy.
Further notes
Further information on characteristics is available in this Customizing activity via Help -> Application help.
Customer exits
Customer exit M06E0004 enables you to change the communication structure for determining the release strategy for purchasing documents.
Edit Class( CL02 )
In this step, you create classes for a release procedure for purchase orders (POs).
You use a class to group together characteristics that are to constitute a release condition for a release strategy. In the step "Define Release Procedure for Purchase Orders " you assign this class to the release strategy.
Activities
1. Create a class with the class type 032. You have a free choice of names for the new class (e.g. REL_RFQ for the release of RFQs).
2. Assign a name for the new class on the tab page Basic data.
3. You can view an error message if different characteristics with identical values have been assigned to a class. To be able to do so, select the Check with error message indicator in the Same classification area.
4. If appropriate, select terms to be used as search criteria in searches for your class on the Keywords tab page.
5. Assign your characteristics to the class via the tab page Characteristics.
Further notes
Further information on classes is available in this Customizing activity under Help -> Application help.
Define Release Procedure for Purchase Orders
In this step, you set up the release procedure for purchase orders (POs) and can link it to workflow. (Note that in this context "releasing" means "approving", or giving the "green light" to a document.)
Requirements
· In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
· You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).Activities
Here you define the following:
· Release group
· Release codes
· Release indicator
· Release strategy
· Workflow
Release group
Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure.
Release codes
Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field
The Workflow indicator is also used to control role resolution:
· "1 - Role Resolution with Group, Code and Plant (T16FW)"
Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
· "9 - Role Resolution via User Exit"
Here you use the customer exit M06E0005 to define a role resolution of your own.
Release indicators
A release indicator shows the release status of a PO.
Via the following settings, you can define the release indicators you need for your release procedure:
· The Released indicator is used to specify whether messages (PO documents in output format) may be transmitted for a purchase order with this indicator.
· The Changeability indicator shows the effect of changes to the PO (a change to a PO may require a new release strategy to be determined, for instance).
· By means of the Value change indicator, you can specify that the release strategy is to be re-started if a PO is changed and the value of a PO item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.
Attention:
The following release indicators are necessary for every release procedure:
o Release indicator for initial status
If the PO is subject to a release strategy, it must normally be released before it can be transmitted to the vendor. Therefore, when a PO is created, it is assigned a release indicator that blocks it from being outputted in message form.
The Released indicator must not be selected for this indicator.
o Release indicator for released status
This indicator is assigned to the PO when it is released.
The Released indicator must be selected for this indicator.
Release strategies
Create a release strategy for your release group and assign your release codes accordingly.
· Release prerequisites
With the release prerequisites , you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document.
Example
The following table shows release prerequisites for a strategy with four release codes.
Code/Release prerequisite
01 02 03 04
01 -
02 -
03 -
04 -
In this release strategy, the codes 01, 02, 03, and 04 must successively release the purchase order.
Read the table from left to right. For instance, the third line for release code 03: For code 03, release via code 01 and code 02 is a prerequisite. That is to say, the PO must be released via codes 01 and 02 before it can be released via code 03.
· Release statuses
Here you specify the status a PO has after certain release points have effected release.
Specify which release indicator/status a PO is to have after having been released via a certain release code.
· Classification
In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the POs to which your release strategy is assigned.
Maintain values (individual values or intervals) for your characteristics.
Example
Two characteristics and their values have been maintained in classification for release strategy 'EA':
- Document type - 'NB - standard purchase order'
- Total value - above $10,000
All POs with the document type 'NB' and a total value in excess of $10 ,000 are thus subject to a release procedure with the release strategy 'EA'.
· Release simulation
The release simulation function enables you to check which status a PO will achieve with your release strategy if release is effected by a certain release point.
Choose "Simulate release" and release the document with the desired release code by double-clicking. The system shows you which status the PO now has as a result of this release.
Workflow
Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
You can assign a processor ID either directly or indirectly:
o Direct processor assignment:
Enter a user name.
o Indirect processor assignment:
Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
Customer exit
Customer exit M06E0005 enables you to define your own role resolution which determines the person responsible for releasing purchasing documents in workflow.
Further notes
Further information on how to set up a release procedure linked to workflow is available via the menu options Help -> Application Help.
Check Release Strategies
In this step, you can check whether the basic settings for your release strategy are complete and correct.
Checks
The following checks are carried out for purchasing documents:
· Basic checks
The system checks whether the necessary release groups exist in the system. For example: Whether a release group has been deleted even though an associated release strategy still exists.
· Checks regarding release groups and release classes
The system checks whether the release groups and the assigned classes have been maintained correctly. For instance, whether
o A class has been assigned to the release groups and whether it exists in the system
o Characteristics - which exist in the system and are linked to the communication structure - have been assigned to the class
o A customer exit must be maintained for a characteristic
· Checks regarding release codes
The system checks whether the release codes have been maintained correctly
· Checks regarding release indicators
The system checks whether the release indicators have been maintained correctly. For example: Whether release indicators exist for the statuses "Blocked" and "Released".
· Checks regarding release strategies
The system checks whether the release strategies have been maintained correctly. For example, whether:
o Release codes have been assigned to the release strategy
o The relevant release indicators have been assigned to the initial and final statuses of a release strategy
· Checks regarding link to workflow
The system checks whether the link between your release procedure and workflow has been maintained correctly. For example, whether:
o A processor (member of staff responsible for processing) has been assigned to a workflow-relevant release code and is defined in the organizational plan
o A customer exit is necessary for the role resolution
Result
The result of these checks is displayed in a log. Further information is available in the Customizing activity under Help -> Application Help.
Activities
1. Start the check by performing the Customizing activity.
2. Check whether any error or warning messages are displayed.
3. If necessary, correct your Customizing settings for the release procedure.
4. Re-run the check after making corrections.
Rewards if Helpful
Regards
Sanjay L
Maybe you are looking for
-
I have an oder Ipod shuffle with many songs loaded on it. How can I transfer ths songs to a new computer since the old computer is no longer available?
-
Hi, I am installing the SharePoint-2013 on development virtual machine. and i have the following environment. Windows server : 2012 SQL server 2012(enterprise edition) Active directory(domain) is configured on same server. for SharePoint configuratio
-
I have a new laptop because my old one crashed. How do I recover my songs not purchased on itunes?
-
HP Network Printer + windows 7 64bit
Hi I have a PC which I am using as a Printer Server. I have install 2 HP printers on it. One Colour(Clolor Laserjet Cp1515n) and other Black white (LaserJet 2300n). I am also running an autologin script on my main server which installc and connect my
-
I guess I installed something I shouldn't have. So I have a idea where all the themes are on the phone, but what folder hold all the programs. I need to delete that folder and start over from there? O can't even boot up my phone when my cards in ther