Transaction Variant - A Step by Step Guide for Creation

Summary

Transaction variant is a very efficient method to create some tailored version of standard SAP transaction without any actual modification. This article explains in a stepwise manner how to do that. The transaction chosen is CO01 - Create Production order. 

Introduction

Transaction variants are created to personalize any standard SAP transaction. A transaction variant simplifies the usage of a transaction by tailoring some of the features as per the business need. It can be used to hide fields, menu functions, screens, to supply individual fields with default values or to change the ready for input status of one or more fields.
This document describes the step by step process to create a transaction variant for standard SAP transaction CO01 - create production order. The transaction variant should have the following restriction:

·         Order type is not visible in the initial screen.

·         Menu path Order -> Create from Planned Order is deactivated

There are two steps, first create the transaction variant and then attach the transaction variant to a transaction.

Creation of Transaction Variant

Transaction variant can be created by through transaction code SHD0. The steps to create a transaction variant as follows:

1.     Go to transaction SHD0. In the initial screen enter the transaction code (in this case CO01) for which we are going to create the transaction variant. Enter the name of the transaction variant (say YCO01) in the "Transaction Variant" field and then click the "Create" button.

2.     In the next screen transaction CO01 will be opened in recording mode. As we are going to hide the field "Order type", enter some default value (say PP01) in that field. For others we may or may not enter values. Click "Enter". A pop-up screen will appear.

3. In the "Confirm Screen Entries" pop-up screen we can customize the fields. Enter the screen variant name (say YCO01_0100) and short text (Test screen variant) here.  Also for the field "Order type" check the Invisible checkbox to hide this field from the screen.

4. To deactivate some of the menu function click the button "Menu functions".  A pop-up screen will appear. In the pop-up select the menu item "Order-> Create from planned order" and click the deactivate button.

5. The menu item will be deactivated (it will be highlighted in yellow). Click "Enter" to come back to the original screen entries pop-up.

6. Click "Exit and Save" button to save the Transaction variant. System will pop-up for a transport request. We can save it as a local transport or save it in some transport request.

7. We can test the transaction variant by clicking the "Test" button in the initial screen.

Assigning Transaction Variant to Transaction Code

After creating the transaction variant we need to assign it to a transaction. The transaction can be used by the user to get the required tailored version of the original transaction. The steps are as follows:

1. Go to transaction SE93. Enter the name of the transaction code (say YCO01_TCODE ) to be created and click the button "Create".

2. In the next pop-up screen enter the short text, select the radio button variant transaction and click enter.

3.     In the next screen enter the transaction (CO01) and transaction variant (YCO01) created in the previous step. Click the "save" button to save the variant transaction.

The variant transaction (YCO01_TCODE) is now ready and it can be used to get the tailored version of the original production order creation (CO01) transaction code.

Result:

Initial Screen: Field "Order type" is not visible

Menu: Menu item "Create from planned order" is disabled

CKM3 is the collective cost analysis developed to consolidate material values.

CKM3 is the collective cost analysis developed to consolidate material values.

It is a amazing tool to detail collectively the actual costs of material in different months and categories after the execution of Material Ledger.

So, In this transaction CKM3N Collective we can see a lot of detail and informations colletively per month or per type of materials. There are many filter of selections that is a facilitor when we need to check a big range of material every month.

The program CKM3 Collective was developed with standard functions “MLCCS_KEPH_MLCD_READ'', that is used to get the cost  standard stratification , easily! The second one , ''CKMCD_MLCD_READ''  this functions was important to find  the ''multilevel difference'' and ''no allocated'' within two categories ; Receipt and production.

Details:

Tables CKM3 Collective : CKMLHD, CKMLKEPH, MARA,MBEW, TCKH3 ,TCKH1, CKMLCR,MLIT and MLCRF

t is a amazing tool to detail collectively the actual costs of material in different months and categories after the execution of Material Ledger.

So, In this transaction CKM3N Collective we can see a lot of detail and informations colletively per month or per type of materials. There are many filter of seletions that is a facilitor when we need to check a big range of material every month.

The program CKM3 Collective was developed with standard functions “MLCCS_KEPH_MLCD_READ'', that is used to get the cost  standard stratification , easily! The second one , ''CKMCD_MLCD_READ''  this functions was important to find  the ''multilevel difference'' and ''no allocated'' within two categories ; Receipt and production.

Details:

Tables CKM3 Collective : CKMLHD, CKMLKEPH, MARA,MBEW, TCKH3 ,TCKH1, CKMLCR,MLIT and MLCRF

First function :MLCCS_KEPH_MLCD_READ

  CALL FUNCTION 'MLCCS_KEPH_MLCD_READ'
    EXPORTING
      i_refresh_buffer = abap_true
      it_kalnr         = lt_kalnr
      i_from_bdatj     = p_bdatj
      i_from_poper     = p_poper
      i_to_bdatj       = p_bdatj
      i_to_poper       = p_poper
      ir_keart         = lr_keart
      ir_mlcct         = lr_mlcct
      ir_kkzst         = lr_kkzst
      ir_curtp         = lr_curtp
    IMPORTING
      et_keph_mlcd     = lt_keph_mlcd.


Second function :CKMCD_MLCD_READ

CALL FUNCTION 'CKMCD_MLCD_READ' "
* EXPORTING
*   i_to_poper =                " ckmlpp-poper  Posting Period
*   i_untper =                  " ckmlpp-untper  Value Structure Type
*   i_run_id =                  " ckml_run_id   Number of Costing Runs for Material Ledger
    .  "  CKMCD_MLCD_READ

Obs: There are many others functions in this development .

Categories:
Beginning Inventory, Production, Receipts, Cumulative Inventory, Consumption, Consumption Production, Ending Inventory

First screen ( Data selection)

Second screen 

1. TMAT( type of material )
2. Material Code
3. Short text of material
4. ArAv( Plant)
5. Tp.Aval.
6. Estoque Total =Total inventory quantity 
7. Unit  ( Kilogram= KG);
8. Valor Total = Total Value (Standard cost of material  within the month)
9. Diferença de Preço = Price difference ( Standard value – Actual  value =Price difference  within the month)
10. Valor Real = Actual Value  (Standard value + Price difference  )

How to undelete deleted service entry

Deleted SES can not be undeleted.

Yes if you would have blocked the SES, that can be unbloked.

E-Mail notifications for new work items in the Business Workplace (RSWUWFML2)

Purpose

The report sends notifications for work items by e-mail to SAP users who have an Internet e-mail address. This enables users who do not normally use the Business Workplace to be informed about new work items. The report is used in particular to replace existing SAP MAPI installations. You can also send SAP shortcut attachments using this report. These enable the receiver of the e-mail to display or execute the work item directly, or to open the Business Workplace in the SAP GUI for windows.

In the case of a periodically scheduled run (not a single run), the report generates notifications for work items for which the following applies:

The work items must have the status ready.< LS>

The work items have been created since the last run (the time and date of the last run is saved in a table).

The work items have a receiver with a valid Internet e-mail address.

See SAP Note 733681 for additions to the documentation.

Advantages:

Users who do not normally use the Business Workplace of a particular SAP system because they use another e-mail client or another SAP system, can be notified easily.

Workflow patterns or tasks do not need to be modified.

The generation of notifications does not need to be modeled in Workflow.

Overall performance is improved. Compared with SAP MAPI, this report is better for performance since it determines the work items for all users with just one selection, while each user must select their Workflow inbox individually in the case of SAP MAPI.

Limitations:

Selection only includes newly created work items. Work items that have been reassigned to another user by forwarding or changes being made to the organizational structure are not included.

Normal SAPoffice messages from the Documents folder are not forwarded by the report.

Active substitution is supported, but passive substitution is not. If an agent has specified a substitute, but the substitution has not yet been activated, then the substitute does not receive the e-mail notification for the person he is substituting. This also applies if the substitute arranged the substitution himself.

There is no password caching for shortcuts. If Single Sign-On is not active, the user needs to log on to the system separately.

The messages are generated in text-only format.

A user can be informed about multiple work items in a collective notification. However, the collective notification does not contain details about the individual work items.

Document and object attachments of a work item are not sent.

No container variables or container expressions can be used in the descriptive texts (Before Work Item Description, After Work Item Description).

Messages are generated in the language of the user for whom the report is running.

Messages can only be sent to SMTP addresses (type INT).

Groupware-specific forms are not supported.

Integration

You schedule this report as a batch job.

Prerequisites

The receivers of e-mail notifications must have maintained an e-mail address in the relevant SAP system. You can maintain a users e-mail address in either the central address management (transaction SU01) or the personal office settings in the Business Workplace, under Automatic Forwarding. You no longer need to activate the Mail Group in the general office settings for RSWUWFML2.

Features

Instance data:

Job Suffix:

Using a job suffix enables you to have multiple instances of the report running simultaneously. Note that the times for the last run are saved for the individual instances. You can set the report parameters differently here.

Tasks:

You can restrict the selection of work items to work items for particular tasks. You can select multiple tasks here.

Send granularity:

If you change this setting, then the default settings in the lower frame are changed dynamically.

One message per work item

One message is sent for each new work item. This contains the description of the work item and accompanying texts, as specified under Standard Text for Notification.

Collective message:

Only one message is sent for all new work items for a particular user. The message does not contain any information about the individual work items.

Add executable message attachments for:

Executable attachments are SAP shortcuts that receivers of messages can use to directly display a work item in the SAP GUI for Windows. SAP shortcuts contain the relevant logon language from the central address management (transaction SU01) for each individual receiver. The system ID and the client contained in the shortcut correspond to the system in which the report is running.

Workflow Inbox

An SAP shortcut is added to the message so that the message receiver can start the Business Workplace directly in the SAP GUI for Windows.

Work Item Display:

An SAP shortcut is added to the message so that the message receiver can display the work item directly in the SAP GUI for Windows.

Work Item Execution

An SAP shortcut is added to the message so that the message receiver can execute the work item directly in the SAP GUI for Windows. Secondary methods are also executed at the same time.

Standard message text

This option enables you to define the message subject and text, which is added to the work item description. The text contains general information for the user about what to do with the message.

Message class for subject

Message class of a T100 message (transaction SE91) from which the subject line for the message is determined. Message class SWU_NOTIF contains the messages that are shipped by SAP.

Message number for subject

Number of a T100 message (transaction SE91) from which the subject line for the message is determined. The T100 message can contain two parameters. Parameter &1 is replaced by the system ID. Parameter &2 is replaced by the work item text.

Before work item description

ID of a SAPscript text (transaction SE61) of type Text in Dialog, which is inserted before the actual work item description in the message. The text contains the form of address for the user and the reference to Business Workflow. Ensure that the text matches the send granularity. The system proposes an appropriate text. Includes and symbols within a SAPscript text are expanded. Workflow-specific variables or expressions (for example, from the container) cannot be used, however.

After work item description

ID of a SAPscript text (transaction SE61) of type Text in Dialog, which is inserted after the actual work item description in the message. Ensure that the text matches the send granularity. The system proposes an appropriate text.

SAP shortcut parameter:

Here you can define the ID of an entry in the SAPLogon, which is included as the parameter Description in each shortcut that is sent. This is a useful setting if you want to ensure that the saplogon.ini has the corresponding entry on all user PCs. The parameter is only required if there are multiple saplogon.ini entries for the same system on the users PCs. You can activate an entry of this type individually.

Data for single run

A single run is performed if the input fields contain a data, time, and optionally a user. A single run is recommended if work items are to be sent again from a particular time and date, for example due to a problem when sending the e-mails. Contrary to a periodically scheduled run, in a single run the time of the last run is not saved.

From work item creation date

First day when work items are to be included.

From work item creation time:

Time on first day when work items are to be included.

User:

Notifications are only generated for work items that have this user in the Business Workplace. You must not use this option to restrict the sending of notifications in the productive environment to certain users.

Log:

During its run, the report writes a log in a spool file and an entry in the application log. You can define what is logged:

Errors Only: Only error messages are logged

All: Success and error messages are logged

You can display the application log by calling transaction SLG1. Enter the object=WF and the sub object=NOTIFICATIONS as the selection values.

Properties:

If one message is sent for each work item, the message contains the task description and the standard text. If one message is sent for all work items, the message contains just the standard text. Express mails are sent for express work items.

If the messages include executable attachments, they are sent to each user individually. If executable attachments are not required, all messages that refer to the same work item are sent to a receiver list, which comprises the selected agents.

If you have selected a Collective message, only one message is sent to each receiver per run, regardless of the number of work items for this user.

The results of database queries (for example, e-mail addresses) are buffered to improve system performance.

By making an entry in table SWUTYP2ADR you can specify that all outbound mail messages are send to a specific e-mail address and not directly to the end user. This address can be monitored by an automatic agent who reformats and forwards the mail messages. The table has a maintenance view and can be edited by calling transaction SM30. Add a new entry to the table and leave the field Form Type empty and enter the e-mail address in the Proxy Mail Address field.

The usual logic when using SAP shortcuts applies when logging on to execute shortcuts. If the parameter Description is specified in the SAP shortcut, but there is no saplogon.ini entry with this name, the system displays an error message when you attempt to execute the shortcut. If the parameter Description is not specified, a saplogon.ini entry with the relevant system is selected instead. If a session with the relevant entries for system/client/user/language is already open, a new session is opened automatically without the user needing to log on. If no such session is already open, the user must log on again. If the selected saplogon.ini entry is configured for Single Sign-On, the system logs the user on automatically. If it is not configured, the system displays a logon window in which the user must enter their password.

Selection

1. Determine the relevant work items. Dialog work items and missed deadline work items are included. Forwarding and changes to the organizational structure are not included.

2. Determine the receiver for each determined work item. Active substitution is included, but passive substitution is not. Substitute profiles and task classifications are included.

3. Only receivers who have an Internet e-mail address (type INT) are included.

4. Create message body (partly work item-specific).

5. Send the message to all receivers.

Standard Variants

You can define variants for scheduling. If you use multiple variants you must at least use the job suffix to differentiate between them.

Output

You can generate a log file and an application log.

Documentation available in SE38. Read this documentation and always make sure before creating the background with a SAP User Id you run this program in foreground logging with that user Id. 

Movement type 453

453 is used for Transfer posting blocked stock returns vendor to unrestricted-use stock..

so for that you need to create PO then do GR to blocked stock.. then do return to vendor..in MIGO
then use 453 to transfer it to unristricted use


The 453 Movement Type, unlike most Transfer Postings, is actually the point in the process, when the Stock becomes valuated, because the stock is transferred from Returns Stock (Unvaluated) to Unrestricted Stock (Valuated).

Release Procedure for PR With classification In Sap MM CREATION OF CHARACTERISTIC

Materials Management / Purchasing/ Purchase Requisition / Release Procedure /

Procedure with Classification/ Edit Characteristics.



Enter characteristic name (ceban_gswrt ) and click on create button.

Now click on additional data tab

table name : ceban

Field name : gswrt & press enter

In basic data tab enter

Currency : inr &

check multiple values & interval vals allowed as shown below

Now click on values tab & enter as below

Now click on restrictions tab

Enter class type : 032 & press enter, below screen appears

Now Click on save button below screen appears.

CREATION OF CLASSES

Materials Management / Purchasing/ Purchase Requisition / Release Procedure / Procedure with Classification/ Edit Classes.

Enter class, class type, & click on create button.

Enter description

now click on char. tab

& enter characteristic name, & press enter, & save it.

Set Up Procedure with Classification

Materials Management / Purchasing/ Purchase Requisition / Release Procedure / Procedure with Classification/ set up procedure with classification

Now click on release groups

Click on new entriesa

Enter rel.grp, class, description & click on save

Press f3, f3(back) & click on release codes

Click on new entries & enter grp, code, desc as below

Now press enter & click save button.

Press f3, f3(back) & click on release indicators

Click on new entries

Enter release id, changeabile, value change & press save button.

Similarly create another release id as shown below. & save it , press f3 ,f3.

Now click on release strategies.

Now click on new entries

Enter release grp, release strategy, & release codes as below.

Now click on release prerequisites. Check od check box & click on continue.

Now click on release statuses

Observe the below screen and click on continue

Now save it & click on classification

Follow below steps

Check >=5000,00 inr check box & press enter

Now press f3.

Click on release simulation.

Following screen appears & click on simulate release to do release test

Now click on release possible then only OD can release pr.

Now press f3 following screen appears.

Simillarly create release strategies with A3,A2,A1 in GI Group with these conditions

A3 = < 5000 & approval should be by plant manager A

A2 = >=10000 & approval should be by stock controller A & plant manager A

A1 = <10000 & approval should be by stock controller A.

Now create pur.req & we can release this pur.req itemwise.

Creation of purchase requisition

Now create pur.req t.code- ME51N

Enter material , plant, delivery date, quantity & press enter button.

Now press check button below screen appears

Press Save .

Release procedure for pur,req t.code-ME54N

Observe the release strategy tab .

Click on release options in release strategy tab. Now SA is released

Click on release options in release strategy tab again to release PA as shown below.

Click on save button.