In this video, I have provided the business usage of PR Release strategy along with Configuration and Testing. I hope it will be helpful for your learning as the process is explained with simple language.
Please provide your valuable feedback and don’t forget to share with your circle if you like the video
Above error is occurred when the service entry sheet is released for a Service Purchase Order. The reason is the Service Purchase Order contains Planned Delivery Costs. Below are the reasons from SAP Standard to stop Service Entry Sheet.
planned delivery costs are generally not supported in
External Services Management and for blanket purchase orders, item category D
In the business function “LOG_MM_MAA_1”, it is possible to process service purchase order items with multiple account assignment and valuated goods receipts only without planned delivery costs. The design of this business function does not allow planned delivery costs for MAA service purchase order items. When posting the goods receipt for MAA purchase order items, the system checks the data to be posted for consistency. If this data is not consistent, the posting of the goods receipt terminates with error message M7 599. This message should prevent data inconsistencies.
If you enter a return delivery or reversal for an item whose “delivery completed” indicator has already been set, so that the delivered quantity falls below the under delivery tolerance limit, the “delivery completed” indicator is automatically reset. In this case, the system issues a warning message informing you that the “delivery completed” indicator has been reset.
If you are not expecting another delivery, you can reset the “delivery completed” indicator manually. After you do this, the system will no longer change the “delivery completed” indicator automatically.
For all movement types (e.g. 101), for which label printing is desired, you must maintain movement-type-dependent field selection. You will find this Customizing under: Materials Management –> Inventory Management and Physical Inventory –> Settings for Enjoy Transactions –> Settings for Goods Movements (MIGO) –> Field Selection per Movement Type
Include the field WEANZ as an optional or mandatory entry field for the desired movement types. You can add with New Entries
Answer: There are mainly three types of tables and three types of Structures in SAP. I have provided the details of those tables and structures along with examples in this document.
There is a physical table on the database for each transparent table. The names of the physical tables and the logical table definition in the ABAP/4 Dictionary correspond.
All business data and application data
are stored in transparent tables.
Ex: Purchase Order Header Data- EKKO
2. Pooled Table:
Pooled tables can be used to store control
data (e.g. screen sequences, program parameters or temporary data). Several
pooled tables can be combined to form a table pool. The table pool corresponds
to a physical table on the database in which all the records of the allocated
pooled tables are stored. This is for internal purposes, such as storing
control data or update texts etc.
Ex: Material Info Record (Plant-Specific)- A017
3. Cluster Table:
Cluster tables contain continuous text, for example, documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. To combine tables in clusters, at least parts of the keys must agree. Several cluster tables are stored in one corresponding table on the database. This is for internal purposes, such as storing control data or update texts etc.
Ex: Accounting Document Segment- BSEG
A structure (structured type) consists of components (fields) whose types are defined. A component can have an elementary type, a structured type, a table type or reference type
Structures are used specially to define
the data at the interface of module pools and screens and to define the types
of function module parameters.
Structures that are used more than once
can be changed centrally because they were defined centrally. The active ABAP
Dictionary makes this change at all relevant locations. ABAP programs or screen
templates that use a structure are automatically adjusted when the structure
Ex: MEPO1220- Fields for Screen 9101
5. Append Structure:
An append structure defines a set of fields that belong to another table or structure but are treated in the correction management as a separate object.
Append structures are used to
Ex: ISAUTOLAB- IS AUTOMOTIVE Enhancements in EKPO
6. Generated view Structure:
In activation a structure is
generated for a view. This structure serves as interface for the runtime
environment. It does not generally appear in the ABAP/4 Dictionary. This is for
internal purposes, such as storing control data or update texts etc.
Ex: V_T438M_B- Direct Procurement
We can see the type of table or structure by displaying the details with SE11 T Code for a single entry and for multiple tables or structures, we can get from table SAP Tables-DD02L. Both the methods are explained below
1.Through SE11 Transaction Code:
Input Screen: Input the Table which you want to check and click on display icon as shown below
Output Screen: The table or structure type will be visible as shown in the highlighted box
2. Through Table DD02L: This method will be helpful to know the table types of many tables
I hope this document is helpful for you. Provide your feedback. Thanks for viewing the document