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
Purchase Requisition is an internal purchasing document and Purchase order is an external purchasing document which will be shared with Vendor to get the ordered materials. We can get the Purchase Order details which are created with reference to respective purchase requisition by using below logic. The PO creation date and time details can be taken by following below two steps
Step 1: Pass Purchase Requisition (BANFN) in EBAN table and get Purchase Order (EBELN). Below screenshots are provided to understand the input data and output data. Transaction code which is used for below screenshots is SE16N
Input Screen is provided below where the Table and Purchase Requisition field are highlighted
Output Screen is provided below where the Purchase order field is highlighted
Step 2: Pass above Purchase Order Number (EBAN-EBELN) as OBJECTID , Application object Change id (CHANGE_IND) = I in CDHDR table and get the PO Creation Date (UDATE) and time (UTIME) as shown below
Input data is provided below by highlighting the Table and input fields
Output data is provided below where the required fields Date and Time are highlighted
We can use this logic when you get the requirement to fetch PO creation date and time for any custom report and smart forms. I hope this document is helpful for you. Thanks for viewing the document. Please provide your valuable feedback and share with your network.
Answer: We can block a Storage Bin with Transaction Code LS02N- Change Storage Bin or Transaction Code LS06- Block/Unblock Several Storage Bins simultaneously. We use LS06 when we want to block multiple bins at a time based on business requirement. In this document, I have explained the process of Blocking Storage Bin for Stock Removal along with testing document which will be helpful to understand the requirement.
Generally business use this functionality when they want to block specific Storage Bins due to maintenance activities or repairing work or temporarily no use or blocked the stock for specific business purposes. Based on business requirement, we will create multiple reasons in configuration.
1.Master Data Change:
Updating Stock Removal indicator and Reason for a Storage Bin with LS02N Transaction Code. We can configure multiple Blocking Reasons based on business requirement which will be assigned during the process of blocking.
Once you flag the stock removal check box and input the suitable reason for blocking, you need save.
Once you click on save, system will give below successful message.
You can display the Storage Bin with Transaction Code LS03N where the blocking reason and block indicator can be seen. You can find below screen where I highlighted the key fields
We have completed the blocking of Stock Removal for the Storage Bin A-0-1. Now we will do the testing to understand the use of blocking and how does it help business to stop picking or stock removal from specific Storage Bin
As part of testing, I have taken a Storage Unit which belongs to the Storage Bin A-0-1. Now we will try to transfer the Storage Unit to other storage Bin. You can get the list of Storage units of the bin from standard SAP Reports like LX02/LX03
Display Storage Unit- T Code – LS27
Input Storage Unit and click enter to get the Storage Unit details. You can observe the storage type and bin on the screen.
Now we will test the process of creating Transfer order to move the Storage Unit 1000000036 from A-0-1 to any available storage bin to check the system behavior.
Create Transfer Order with Storage Unit: T Code- LT09
Go to the Transaction Code LT09 and input Storage Unit which needs to be moved along with movement type 999 as shown in below screenshot. After inputting the details, you need to click enter.
Once you click enter, system shows below screen. Check the source details like Plant, Storage Location, Storage Type and Bin etc. Then click on Create Transfer Order. If you want to transfer to specific storage bin, you can input otherwise system will fetch destination storage bin details based on Putaway Strategies.
Once you click on Create Transfer Order, system gives below error message as the source storage bin A-0-1 is blocked for stock removal.
I hope this document is helpful to understand the business requirement and respective solution. Until you unblock the storage bin, system won’t allow to remove/pick any stock from that storage bin.
Thanks for viewing the document. You can share with your network if you like the document and explanation.