Settlement: Since batch material price indicator is V, therefore settlement of balance amount happens on material.Image may be NSFW. Clik here to view.
In this document we will learn about two different methods to identify authorization issues.
SU53 or /nSU53
ST01
SU53 or /nSU53
Using this transaction you can analyze an access denied error in your system that just occurred. It displays the last failed authorization check, the user’s authorization and the failed HR authorization check.
Scenario:
User gets an authorization error on releasing a notification from IW22 transaction
These values can be used in SUIM transaction to identify the roles which you can assign to user.
ST01
ST01 is one of the primary tools in the SAP Security Module. ST01 gives us a peek inside running ABAP program or standard transaction to record the SAP Authorization checks in your own or external system. The trace records each authorization objects, along with the object’s fields and the values tested.
Scenario:
User is having access to perform “Do not Execute” in the work order, need to restrict the user with the functionality.
This particular access cannot be captured via SU53
IW32:
When the Work order is in CRTD status, system will allow you to set “Do Not Execute” from the Path Order – Functions – Complete - Do not Execute
This step demonstrates how completion confirmations for a production order can influence maintenance measures performed on production resources and tools. This example has been created for a bottling/canning plant. Here, tins are filled with paint. The bottling/canning plant contains a filter press which is recorded as PRT equipment in the task list for material Y-351.The maintenance plan for the PRT equipment contains three performance related maintenance cycles. This means that every time the PRT equipment above is used, different operations are used for the scheduled maintenance plan. In cases of high use this may lead to a change of filter
You have confirmed the order. A measuring point was defined as a production resource in the task list, enabling the SAP system to create a measurement document. This document creates a new call after the maintenance plan has been scheduled.
Overview: Pool asset management (PAM) allows an organization to manage its pool assets using a graphical planning board. Examples of pool assets can be vehicles, beamers, laptop etc. In this document, I will take an example of pool asset as vehicle to go through the different steps. By using PAM, a planner can request, issue, return and then finally settle the service provided using the graphical planning board.
Steps involved in PAM:
The entire end-to-end scenario for PAM involves below steps:
1) Creation of demand
2) Demand Planning with Graphical Planning Board
3) Issue of pool asset
4) Return of pool asset
5) Settlement
Before I go into detailed steps, I would like to mention some pre-requisites that must be fulfilled before this scenario is run:
1) A functional location is created and all pooled equipment (vehicles) installed at functional location
2) A pool of vehicle is created using transaction code PAM01 and functional location assigned to this pool
3) Equipment created as pool asset must have a measuring point assigned for odometer reading and PAM category (PCM_KAT) assigned in equipment characteristics
Now, let's go through all the steps for pool asset management in detail:
1) Creation of demand:
Demand can either be created by a requester or a planner. Let's assume that the demand is created by a requester. This is done by using transaction IW21 for creating a notification with a standard notification type MF.
Requester enters user and requester information along with notification description exp. 'Request vehicle'.
After the requester uses the vehicle and returns the vehicle back, planner will then enter the details in the system (such as new odometer reading) by double clicking on the green bar. This changes the green bar to a small line on the planning board.
In this document we will be going through various steps involved to develop Multiple counter plan.
A multiple counter plan is used in counter based maintenance. This type of maintenance planning is not based on a maintenance strategy. This means that you can create a multiple counter plan without maintenance strategy.
Master data requirement
Below are the list of basic Master data required to process Multiple Counter Plan.
Equipment
Characteristics for measuring point / counter
Measuring Point/Counter assigned to Equipment
Cycle sets as per requirement
Equipment - IE01 / IE02
I have created PUMP as Equipment for explaining this scenario.
On save, first measurement document created for measuring point / counter. Two documents are posted for this measuring point / counter.
Cycle Sets - IP11Z
Cycle sets are used as a copy model for the creation of multiple counter plan. It defines the period of time between two maintenance tasks. Also cycle sets can be complied directly in multiple counter plan itself.
Cycle sets needs to be created based on business requirement.
Cycle set sequence needs to be filled and same has to be linked to maintenance item. Here the scenario has only one cycle set sequence.
Cycle set sequence, Scheduling period, Start date will be populated in the multiple counter maintenance plan (IP43) after activating the "Configure Special Functions for Maintenance Planning" in SPRO.
Kindly update the maintenance plan with relevant details like Maintenance Plan Description, Maintenance Item Description, Order Type, Planner Group, Work Center, Task list and Priority.
In this document we will discuss what is the Permit and what are the types of it (Technical Permit)
Note:The below steps are applied on SAP ECC6.0 EHP6.0
Table OF Contents:
1- Introduction
2- Technical Permit
2.1 Create theTechnical Permit
2.2 Assign The Technical Permit To The Technical Object
2.3 Technical Permits Influences The order
1- Introduction
Permits are created for the Maintenance Order to:
Adhere to health and safety regulations
Control order processing (Release - Completion<TECO>)
There are two types of permits:
Technical Permits (assigned manually to the technical objects (Equipment - Functional Location)
If an order is created for the technical object, the permits are copied to the order and can influence the order release Or completion<TECO> (Depends On Your settings)
2. Process-Oriented Permits (automatic assignment to the order)
e.g. -> when creating a maintenance order with an order type and an activity type , the permits are copied to the order and can influence the order release Or completion<TECO> (Depends On Your settings)
2- Technical Permit
Steps:
Create The Technical Permit
Assign the Technical Permit To The Technical Object
Technical Permit Influences The Order
2.1 Create The Technical Permit
SAP ECC Menu: Logistics -> Plant Maintenance -> Management of Technical Objects -> Environment -> Permits
T Code: IPMD
Click On (Create/Change) Button To Enter The Change Mode
The 1st Option -> when you release the order, a warning message appears but if you pressed Enter, you can continue processing the order
The 2nd option -> The order can not be released until the authorized user issue (Approve) the permit
The 3rd Option -> No Warring Message, just check the permits
Not Modifiable Field: Used when you select the 2nd option as the user can not flag (Dimmed) the button not relevant (Ignore The Permit) when the permit influence the order as The Permit must be issued by the authorized user
Note: We Will Work On Order release
2.2 Assign The Technical Permit To The Technical Object
Note: We Will Assign The Permit To An Equipment -> T Code: IE02
In this document we will discuss the Process Oriented Permit
Note:The below steps are applied on SAP ECC6.0 EHP6.0
1- Introduction
Process-Oriented Permit is assigned automatically to the Maintenance Order
e.g: when creating a maintenance order using an order type with an activity type , the permits are copied to the order and can influence the order release or completion (TECO) -> (Depends On Your settings)
In our example we will create a permit that control the order release when creating an order with:
Order type: PMM1 and Activity Type: A02 0r A03
2- Steps :
2.1- Create two characteristics that represent (Order Type - Activity Type)
2.2- Assign the two characteristics to the permit class (PM_Permit)
2.3- Create the permit
2.1- Create Characteristics (T Code CT04)
Enter the Name of The Characteristics Then create button
As soon as I'm done with my step-by-step reply to a discussion on the subject matter recently, I realized that this long reply comprising of several Screen-captures possesses the characteristics of a Document. So I thought of converting it into a Document, so that members will be benefited from this frequently asked query.
Topic dealt here is for IP30 (program RSITRA20), but this method is valid for other programs too for background scheduling.
Here we see, how to do:
Step1. Create IP30 Variant.
- Run IP30,
- Give your Plan (here it is ABC123 ) in the Maintenance Plan field (Do not forget this step)
- Click Save Button and in the resulting screen give the Variant name,
- Optional:- Tick Only for Background Processing and Save again.
Two Dumpers, with SAP Equipment Ids V-1000 and V-1001, each having 6 Tyres as shown above.
V-1000 with tyres say TYRE0001, TYRE0002, TYRE0003, TYRE0004, TYRE0005, TYRE0006
And
V-1001 with tyres say TYRE0007, TYRE0008, TYRE0009, TYRE0010, TYRE0011, TYRE0012
(External numbering is used for easy understanding)
Each Dumper above has a meter showing the number of hours it operated.
The Objective
When we record a reading from the above meter in the SAP system (using IK11, on a Measuring point), the counters of the 6 Tyres installed in this vehicle at this time, shall be automatically updated.
This means when we create one measuring document on the vehicle, system should create a total of 7 (1 + 6) , measuring documents so that the usage hours flow from the Vehicle counter to the Tyre counter.
And then, when a Tyre is dismantled from one vehicle and installed in the other, the Tyre counter should derive its own usage hours from the present vehicle counter readings.
Let’s see how this happens:
Part1:
Preparing the Masterdata:
First let’s have a characteristic RUNNINGHOUR as shown below (Tcode CT04).
End of Part1 ------------------------------------------------------------------------------------------------------------------------------------------------
Part2a:
Create Documents and understand the working of Transfer Support.
It is time now to see what happens when we record Dumper Hour Meter readings through IK11.
Create a measuring document on measuring point 3113 (Equipment Tyre0001), with reading 1000.
Let’s assume that the Dumper V-1000 operated for 1000 hours and its meter is showing a value 1000 Hours. We now create a measuring document to record this value.
Note:
Remember that we get the Cumulative Operating Hours from the Dumper Meter. So, we need to put this reading in the Counter Reading field of the IK11 screen.
This is exactly what we expect from the system. As explained above 1 document is what we have created just now and the other 6 documents are automatically created for the Tyres. This means the Usage Hour counter for all the 6 Tyres started with their first reading as 1000 hours.
Likewise when we create a document with value 500 hours for Dumper V-1001 (Measuring point 3114). Measuring documents are automatically created for Tyres TYRE0007 to TYRE0012, with this reading of 500 hours.
End of Part2a ------------------------------------------------------------------------------------------------------------------------------------------------
Part2b:
Let’s now see what happens when Tyres are relocated from one vehicle to the other.
We will examine a case of TYRE0004 is dismantled from Dumper V-1000 and installed in V-1001.
And TYRE0009 is dismantled from Dumper V-1001 and installed in V-1000.
When we try to dismantle TYRE0004 from V-1000 through Tcode IE02, we get this warning message.
We can understand what the message says, It is stopping Reading transfer for this equipment (TYRE0004) from V-1000.
We continue and give value V-10001 in the Superord. Equipment field. Now we get this screen (already seen before once), asking for confirmation to establish transfer relation with the new Superord. Equipment.
I have created a document with reading 1450 hours on V-1000 (Measuring point 3113) and a document with reading 1850 hours on V-1001 Measuring point 3114).
Now see the IK17 screen below in the sequential order of Document creation.
The upper half (Green) is before the Tyre swaps, and the lower half is after.
Give special attention to Swapped Tyres (TYRE0004 and TYRE0009) to observe the system intelligence, in transfer of readings during Sub Equipment relocations.
For better understanding Equipment-wise sorted list of above is attached herewith.
End of Part2b ------------------------------------------------------------------------------------------------------------------------------------------------
Note1:
One more thing that happens in the system background during this process was not shown in pictures above.
That is when we click Copy during Equipment installation under a Superord. Equipment in IE02, some changes happen in Measuring Point data (obviously),
i.e. in IK03 screen, which is shown in the field marked below.
As soon as we install TYRE0001 under V-1000, the field marked above is filled with the measuring point of V-1000.
Similarly this field is updated whenever Equipments are relocated from one place to other.
Note2:
In this demo Equipment – Sub Equipment scenario has been dealt.
This document is valid for Functional Location –Equipment Scenario also.
Concluding Remarks
Here, a vehicle scenario has been taken for demonstration of this Measurement Reading Transfer Support functionality of SAP. It is believed that there will be several other applications requiring this feature.
A client wants that Notification Tabs should appear selectively for Create (IW21), Change(IW22) and Display(IW23) views. For example, he does not want to provide Catalog & Codes tab (10/Tab10) during Create Notification (IW21).
Once we know the configuration point in SPRO, where to do this, this requirement looks simpler. But, more work is involved here. This document, elaborates the same.
Please note that the ‘H – Add’ means Create and relates to IW21 screen. Similarly 'V – Change' and 'A – Display' options relate to IW22 and IW23 screens respectively.
Now suppose a Notification type has the requirement for 3 main pages viz.,
10/Tab01– Notification 1
10/Tab07 - Dates
10/Tab10– Catalogs & Codes
We know that 10/Tab10 will have sub tabs declared 20/Tab01, 02, 03, 04.
The following is the Tab strip Overviewin the SPRO, where no special conditions are required. Here we see the Activity Cat.field is blank.
In this Configuration, all tabs will be visible in all stages (IW21, IW22, IW23)
What we see here is for one simple condition, a number of line items added into the 'Tab strip Overview'.
This is because,
When we specify a value V in Activty Cat. Of 10/Tab10 (desiring to have this tab in change mode), all other tabs in change mode disappear. (10/Tab01, 10/Tab10).
So to restore them as per our requirement, we need to repeat these Tabs with different values of Activity Cat. (H, V, Aas the case may be) .
In Detail:
We want the Header Tab (10/Tab01) in all modes Create, Change, Display (IW21, IW22, IW23) modes. So we need to create this entry 3 times with values H, VandA.
We want the Dates Tab (10/Tab07) in Change and Display (IW22, IW23) modes only, so we had this 2 times with values V and A
Like-wise we want the Catalogs & Codes Tab (10/Tab10) also in Change and Display (IW22, IW23) modes only, so we had this 2 times with values V and A.
Here note that all the sub tabs (20/Tab01,02,03,04) of Catalogs & Codes Tab, had also to be created 2 times with values V and A to match with their Parent tab (10/Tab10).
(We know that Catalogs & Codes tab would appear in Display i.e., IW23, only when it has some content in its inside tabs.)
Like-wise we can customize deeply in this area as per need.
The Author recently was replying in detail, about the topic discussed here in an SCN thread, and felt that forum will be benefited if this is documented .
The author believes that the tip given in this document simplifies and drastically cuts down the amount of data upload to QS41 transaction, In fact this tip should be made use of invariably by every-one who designs the Catalogs & Codes to the Equipments.
What is it?
An addition of character ‘&’ at the end of Code Group Description helps the Code-text (kurztext) to be very short, but while using the Code-texts are prefixed by Code Group Texts giving full meaning.
This is being explained through Screen-captures in the following example .
1. The above explanation is applicable for all Catalogs (B,C,2,5, A & others).
2. Because this is a change in Description field, it is applicable to the Code Groups created and used earlier. Accordingly, the Code-Texts will be modified in all History Notifications.
One of the very frequently asked questions in this space, is about the subject matter, i.e., How can I add Custom fields to my Maintenance Order? In the recent months the author had replied 3 times to discussions related to this topic. It is thought that this topic if documented would be helping many.
Objective
This documentation is intended to enable the readers to create the Custom fields in the Maintenance Order, update the Order Master data Table and also display these fields in IW38 Order list output.
Let's Start
Part1
Create Custom fields in the Order Table
The table of our context is AUFK. We need to append our Z-fields to this through the include structure namely CI_AUFK.
The process of creating any custom field starts with creating a Data Element with desired Type and Length or with desired Domain name and with the Field Labels we want to have for the Customer fields. For our Demo, we have created Two Data Elements, namely :
1. ZCUSTFLD1 (Domain CHAR12 and Field Label ‘Customer Field 1’)
2. ZCUSTFLD2 (Domain CHAR40 and Field Label ‘Customer Field 2’)
Now let us create our Customer fields Run Tcode SE11 --> give value AUFK in the Database Table field -->Click on Display. Scroll-down to find include table CI_AUFK. Double click on this, Go to Change mode and Add 2 new fields of our interest as shown in the picture and Activate.
As seen in the picture, we have created Two Customer-Fields namely ZZCUSTFLD1 and ZZCUSTFLD2. It is essential for all Customer fields used in Enhancement purposes to be prefixed with ZZ. Activate the Structure.
Part2
Enhancement and Screen-Exit
1, Create an Enhancement Project say ZPMORDER using Tcode CMOD.
As we see here, there is One screen-exit (screen 0900) and Two Function-Exits namely EXIT_SAPLCOIH_018 and EXIT_SAPLCOIH_019 in this enhancement. Double Click on this screen number to create a Sub-Screen for holding our Custom Fields. You’ll get this pop-up. Press Enter and Continue.
Create a Maintenance Order (IW31). You will see an Additional Tab named Enhancement has been added here by the system, in which our Custom fields appear with their labels and the input fields.
Run IW32, open the Order and verify whether the values are updated to table or not. If they are appearing in the Enhancement tab as you have entered and saved, this means the AUFK table has been updated with these values when Order was saved.
Part4
Let's have these Custom fields in the Order list output namely the ALV of Tcode IW38
So far we have succeeded in creating our Custom fields and updating the values to the Order Master data. Next natural requirement of a user would be to have these fields in IW38 ALV screen. For this purpose we, need to create an Append Structure in the Structure RIHAUFK_LIST, as shown in the picture below. The
Tcode is SE11 again for this task. Here we have created an Append Structure named ZCUSTFLD and in this structure we have added both the Custom fields.
Now let's create one more Order, fill the custom fields with some values and Save. The second order is to have ALV output in IW38. (Because single Order in the output takes to IW33 screen instead of ALV screen). Now run IW38 with selection parameters to display these 2 orders we created. Click on the icon shown , You'd find the Custom fields in the Column-set list, Bring them to Displayed list on the Right hand side.
Now if you go to IW33, unlike all other greyed-out fields, the Custom fields in Enhancement Tab will be seen Editable. Though there is no provision to Save the edits here, you’d definitely like to have these fields too in Greyed-out mode.
For this we need to write a small code in the PBO (Process Before Output) module of the screen 0900 we have created. Double click on the Screen number 0900 of the enhancement,
Un-comment line MODULE STATUS_900. and D’Click on the STATUS_0900 of the PBO module. Insert the following code between the MODULE, END MODULE lines like this.
...... and thus we reach to the end of this knowledge sharing Documentation.
Note
1. As this is largely a Technical job, it is recommended to be developed through an experienced ABAPer, especially Part1 which involves Activating the Standard table AUFK.
2. The Environment of Author is ECC 6.0 with no EHPs, hence the document applicability.
Expecting this document too would be of use to many of the members,
Often there are requirements like having a common large tasklist for a category of equipments and choosing the operations selectively into the Maintenance Order depending upon the equipment specifications on which the order is being made.
Let me explain with an example:.
Suppose there are 100 motors falling into 6 categories as under:
SN
Type
Capacity (KW)
Population
1
Squirrel Cage Induction (SQI)
5.5
20
2
‘’
7.5
30
3
‘’
11.5
5
4
Slip Ring (SLR)
5.5
10
5
‘’
7.5
15
6
‘’
11.5
20
Now the operations to carry-out the work on these machines vary with different ratings (specifications), often due to the variance in the amount of work involved.
We can have all operations of such 6 categories of 100 equipments in a single large tasklist, yet use in maintenance orders created on these equipments.
i.e., While creating the maintenance order, system would choose only those operations from the tasklist which are relevant to the equipment on which the order is being made .
Such tasklist is called a ‘Configurable Tasklist’.
Let’s assume the common large tasklist (General Maintenance tasklist) we have for all these motors is the one shown here, which is to be configured.
System has chosen the relevant dependency operation (0040) and two operations, where no dependencies were specified. (0070, 0080).
This work can be extended to a tasklist of 100's of operations covering 1000s of equipments.
In my experience, very common application has been in Repair shops where equipments like Motors are repaired. Here very few numbers of Configurable tasklists are maintained covering 1000s of motors.
SAP offers the use of IBIP supported objects from within the LSMW to support data transfer.
This abstract explore the "old" option to run transaction IBIP directly with pre made flat files that matches to the IBIP structures and hierarchy ,the Excel IBIP tool can be usesd as an alternative to LSMW
The Tool includes Demo templates are available to Downloadhere
BENEFITS
Authorizations- if your requirement is provide simple excel based tool for the end user for master data management and LSMW authorization in the PRD system is not an option
Fast and Simple - Use 1 Excel source file also for multi structures ,in the IBIP Tool there is no need to link between the files using key relations between the structures ( Using IDENT1 , IDENT2 etc..) as required by LSMW approach , The Flat file records are written to the flat file based on the location sequence of the structure in the Excel template.
Scheduleruns at night Jobs - by splitting the flat file to several flat files we can use the IBIP program to upload the data in a schedule job which includes also the option to define in advance on which servers the scheduled jobs will be executed for load balancing purpose and also achieve "parallel processing" functionality which speed up data upload , This approach is very helpful when dealing with mass master data update , For exemple if several millions of records can be completed over night (depends on the number of servers in the PRD system ) using this approach .
Exemples for such changes for Functional locations or equipments :
- Mass update class and characteristic
- Mass update of system profile
- Mass update of the Address data ( using structure IBIPBDCD)
Templates examples
Exemple 1 :Create Equipment with user status
Exemple 2 :Create Equipment with class and characteristics
Exemple 3 :General Task list with operation and assignment to maintenance packages
Pre requirement
Microsoft excel 2007- 2013
Macro enabled
STEP A - Prepare template - Select the required structuresand required fields
Selected multi radio button
Select structure IBIPEQUI
Select the required fields from the IBIPEQUI structure
Select structure IBIPSTAT
Select all the fields from this structure IBIPSTAT
Step E ( Optional ) store the files in the Application server
Another alternative is to store the flat files at the application server which is mostly required when the data migration duration takes more then several hours and it is required to schedule the run at night (when system load is low) , in this case :
Exemple 2: Equipment creation with class and characteristics
1 Goto transaction IBIP – press the information icon to see Structure hierarchy , So you can know which structures are required to your business scenario Image may be NSFW. Clik here to view.
Catalog-coding functionality covers wide range of applications, hence configured in many different ways to suit the individual requirements.
In this document one such situation has been dealt, where user would like to filter the F4 help of other catalogs as soon as he selects a code-group in object-part (Catalog B).
The End-result of this document
In a Notification, the F4 help in Catalog&Codes tabs Causes, Tasks and Activity, will automatically present the respective codes related to the item selected in the first tab (Object part/Damage). This is done using User-Exit QQMA0015
First, Let's see what is the feature we are talking about:
Select a Code& Code Group in the Catalog-codes tab of a notification.
Upon selecting the ‘DRIVE-SET’ in the Object Part, the filter effect will be activated in the F4 help of all other catalogs, by showing only the Codes of the Code Group with same name (selected in catalog B).
Here on, this is how the F4 help is presented for other Catalogs (Catalog C is demonstrated here)
And assign this Profile (PUMPASSLY) to the respective Equipments.
The F4 help Filter
Write the following Code in the include ZXQQMU21 of user-exit QQMA0015.
FIELD-SYMBOLS : <L_EBENE> TYPE ANY.
IF I_VIQMEL-RBNR = 'PUMPASSLY'. ASSIGN ('(SAPMIWO0)VIQMFE-OTGRP') TO <L_EBENE>. IF SY-SUBRC = 0. IF I_EBENE = 'OT' . MOVE I_CODEGRUPPE TO E_CODEGRUPPE. ELSE. MOVE <L_EBENE> TO E_CODEGRUPPE. ENDIF. ENDIF.
ENDIF.
If in some situation the user needs the filter to be on Damage code groups too,
i.e. When a code group is selected either in Object part or in Damage further catalogs will be automatically presenting the respective Code Groups only.
A code similar to this would satisfy this need.
DATA: C(50) TYPE C VALUE '(SAPMIWO0)VIQMFE-FEGRP'. FIELD-SYMBOLS: <FS1> TYPE C. FIELD-SYMBOLS : <L_EBENE> TYPE ANY. ASSIGN ('(SAPMIWO0)VIQMFE-OTGRP') TO <L_EBENE>. ASSIGN ('(SAPMIWO0)VIQMFE-FEGRP') TO <FS1>. IF SY-SUBRC = 0. IF I_EBENE = 'OT' OR I_EBENE = 'FE'. MOVE I_CODEGRUPPE TO E_CODEGRUPPE. IF <L_EBENE> IS NOT INITIAL . MOVE <L_EBENE> TO E_CODEGRUPPE . ELSEIF <FS1> IS NOT INITIAL. MOVE <FS1> TO E_CODEGRUPPE. ENDIF. ELSE. IF <L_EBENE> IS NOT INITIAL . MOVE <L_EBENE> TO E_CODEGRUPPE . ELSE. MOVE <FS1> TO E_CODEGRUPPE. ENDIF. ENDIF. ENDIF.
Settlement: Since batch material price indicator is V, therefore settlement of balance amount happens on material.Image may be NSFW. Clik here to view.
In this document we will learn about two different methods to identify authorization issues.
SU53 or /nSU53
ST01
SU53 or /nSU53
Using this transaction you can analyze an access denied error in your system that just occurred. It displays the last failed authorization check, the user’s authorization and the failed HR authorization check.
Scenario:
User gets an authorization error on releasing a notification from IW22 transaction
These values can be used in SUIM transaction to identify the roles which you can assign to user.
ST01
ST01 is one of the primary tools in the SAP Security Module. ST01 gives us a peek inside running ABAP program or standard transaction to record the SAP Authorization checks in your own or external system. The trace records each authorization objects, along with the object’s fields and the values tested.
Scenario:
User is having access to perform “Do not Execute” in the work order, need to restrict the user with the functionality.
This particular access cannot be captured via SU53
IW32:
When the Work order is in CRTD status, system will allow you to set “Do Not Execute” from the Path Order – Functions – Complete - Do not Execute
This step demonstrates how completion confirmations for a production order can influence maintenance measures performed on production resources and tools. This example has been created for a bottling/canning plant. Here, tins are filled with paint. The bottling/canning plant contains a filter press which is recorded as PRT equipment in the task list for material Y-351.The maintenance plan for the PRT equipment contains three performance related maintenance cycles. This means that every time the PRT equipment above is used, different operations are used for the scheduled maintenance plan. In cases of high use this may lead to a change of filter
You have confirmed the order. A measuring point was defined as a production resource in the task list, enabling the SAP system to create a measurement document. This document creates a new call after the maintenance plan has been scheduled.
Overview: Pool asset management (PAM) allows an organization to manage its pool assets using a graphical planning board. Examples of pool assets can be vehicles, beamers, laptop etc. In this document, I will take an example of pool asset as vehicle to go through the different steps. By using PAM, a planner can request, issue, return and then finally settle the service provided using the graphical planning board.
Steps involved in PAM:
The entire end-to-end scenario for PAM involves below steps:
1) Creation of demand
2) Demand Planning with Graphical Planning Board
3) Issue of pool asset
4) Return of pool asset
5) Settlement
Before I go into detailed steps, I would like to mention some pre-requisites that must be fulfilled before this scenario is run:
1) A functional location is created and all pooled equipment (vehicles) installed at functional location
2) A pool of vehicle is created using transaction code PAM01 and functional location assigned to this pool
3) Equipment created as pool asset must have a measuring point assigned for odometer reading and PAM category (PCM_KAT) assigned in equipment characteristics
Now, let's go through all the steps for pool asset management in detail:
1) Creation of demand:
Demand can either be created by a requester or a planner. Let's assume that the demand is created by a requester. This is done by using transaction IW21 for creating a notification with a standard notification type MF.
Requester enters user and requester information along with notification description exp. 'Request vehicle'.
After the requester uses the vehicle and returns the vehicle back, planner will then enter the details in the system (such as new odometer reading) by double clicking on the green bar. This changes the green bar to a small line on the planning board.
