SAP PS (Project Systems) Module (II) - In Simple Words.


Network Milestones

Some of the network activities can be maintained as milestones and the list of milestones can be obtained from the database table MLST. In order to get the information of all the milestones of the network the table CAUFV and MLST can be used.

The field CAUFV-AUFPL can be given as an input in MLST-AUFPL and the resultant list provides the list of milestones of the network.

The field MLST_ZAEHL is the Milestone number. This field can be used to get information about milestones from different database tables. For all those purposes, this field can be used as the foreign key.

The field MLST- MLSTN provides the Milestone usage.

If the MS is confirmed then the confirmation number can be obtained from the field MLST- RUECK.

Frequently used Project Systems transaction codes for Network milestone are:



Network Milestone Confirmation Details

The status of the confirmed milestones of a network can be found from the table AFRU. Some of the important fields in this table are discussed below. 

The field AFRU-AUFPL represents the link with all the other tables of the network where this field equals to the field CAUFV-AUFPL or AFVC-AUFPL or MLST-AUFPL. Using this table AFRU can be accessed. 

The field AFRU-VORNR represents the activity number whose milestone is confirmed

The field AFRU-APLZL represents the counter number of the activity in the network. This is nothing but the AFVC-APLZL number.

The field AFRU- RUECK represents the confirmation number. This field is available both in AFRU and also in MLST. However MLST gives the information that the milestone is confirmed but AFRU also says whether the confirmation is a final confirmation or not in the field AFRU- AUERU.

Once this information is known, any other confirmation related information can be extracted either from the table MLST or from AFRU based on requirement. 

Frequently used Project Systems transaction codes for Network Milestone confirmation details are:



Network Material Components

The details pertaining to material components and their assigned transactions can be seen in the tables RESB, AFWD and AFWI. Some key fields of the table RESB are first explained. 

The field RESB- AUFNR represents the network number which triggered the reservation. As this table is the central table for reservation happening from various other transactions like sales order, planned order etc, different fields will be updated during different transactions. If the reservation is triggered through the network, then this field will be filled. For items which do not create reservations from material components, this table is not valid. 

The field RESB- RSNUM represents the reservation number and this can be used to find out all the reservation related data. There are other important fields like requirement quantity and requirement date which can be easily found once this key field is known. 

Similarly, the tables AFWD and AFWI deals with the material movements associated with the confirmation of milestones. Because of my limited knowledge on these tables, I am just mentioning these tables and leave the rest for exploration. 


Status of the Project Elements

There are two tables related to the status of any transaction provided the transaction is enabled for statuses using a status profile. They are JCDS and JEST. There are also two other tables TJ02 and TJ30. 

Any transaction with the status profiles enabled will get updated in tables which will definitely have a field called OBJNR. For example the tables relevant for project, WBS element and network namely PROJ, PRPS and AUFK have this field OBJNR. This field forms the basis for finding out the correct status.  

In other modules transactions include sales order, production order, planned order, maintenance order, task list etc will also have the object number. In sales order object number will be available for both sales order header and item. Accordingly the statuses can be seen both at sales order header and at item level. Similarly each transaction has its own structure and their respective object number. 

The table JCDS shows the change history of the status. The relevant object number OBJNR should be given as the input here and the output should be received. 

Here the field JCDS- STAT represents the status. Any status with the prefix E is the user status and the one with the prefix I is the system status. 

In order to get the correct system, the value from this field should be passed on into the field TJ02-ISTAT to get the system status. 

For user status the field TJ30- ESTAT should be filled with the value of the field JCDS-STAT to know the actual user status. 

The table JEST shows the current status of the object. The same logic should be used as explained earlier. 

There is also a function module STATUS_TEXT_EDIT which can be used to fetch the system status or the user status for any project object, as long as we know the Object number OBJNR of the project element. We can have this value for any project element in the respective table, as already explained. 
If this value is provided as the input parameter, it is possible to get the user status and system status as output parameters. 


PS Master Tables & Their Relationships



Following diagram depicts the linkage between various master tables in PS module.


 


tags: Functional For ABAP, SAP ABAP PS Module, SAP Project Systems, SAP Project Systems basics, sap project systems overview, sap project systems process flow, SAP PS, SAP PS ABAP, sap ps module, sap ps tutorial, sap project system tables, sap ps tables, sap ps module overview,

Comments

Also Read...