In this category, you will get Important Documents and Videos related to SAP MM
Dear All,
In this video, discussion onfew topics of SAP MM are covered. I hope this video will be helpful for your learning. You can watch and share your valuable feedback.
Don’t forget to share with your circle if you like the video
Regards,
Ganesh Padala
ganesh.sap2015@gmail.com
Hi all,
In this video, few important queries from SAP MM are discussed. I hope it will be helpful for you.
Regards,
Ganesh Padala
ganesh.sap2015@gmail.com
Ans:
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.
Regards,
Ganesh
Ans:
No. This is the standard system behavior. Standard systems are not designed to issue all items in one label. However, you can print one label for each collective slip item
Dear Friends
I am uploading one more SAP MM Mock Interview which covers few important questions from SAP MM. I hope it will be helpful for your interviews. Please watch and provide your valuable feedback.
Regards,
Ganesh
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.
1.Transparent table:
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
4. Structure:
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 changes.
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 support modifications.
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
Input Screen:
Output Screen:
I hope this document is helpful for you. Provide your feedback. Thanks for viewing the document
Best Regards,
Ganesh Padala
ganesh.sap2015@gmail.com
Answer:
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.
Thanks and Best Regards,
Ganesh Padala
ganesh.sap2015@gmail.com
Answer: Latest GR date field in Purchase Order item is useful to control the late Goods Receipts. Based on business requirement, this can be used to provide as information to the user who performs Goods Receipt or else to stop GR which happens after the Latest GR date of PO. Generally, business uses this field for information purpose but not to stop GR.
Business can use this field as information or as control to stop GR for the Purchase Orders.
Ex: Delivery date of a PO item is 03.03.2019 and the Latest GR date is maintained as 12.03.2019. And make the message M7163 as E (Error) so system won’t allow any Goods Receipt after 12.03.2019. Similar approach can be used to prompt as information by keeping message M7163 as W (Warning)
Below is the explanation from SAP about the field Latest GR date. I have provided the screenshot from Purchase Order for your reference
This is the latest acceptable date for goods receipt (GR).
If goods are received after this date, you will receive either a warning message or an error message, depending on the system setting.
If you receive an error message, you will not be able to post the GR.
Below screenshot shows the Warning message which will be prompted by the system during Goods Receipt
I hope this document is useful for you. Provide your valuable feedback.
Thanks and Best Regards,
Ganesh Padala
Answer:
We can identify the list of message types which are entered manually for a Purchase order by inputting Purchase Order number in object key field along with input of X to field MANUE. It will give the details of output types which are maintained manually.
Same approach can be used for other documents like Outbound delivery, Shipment etc. If MANUE=Blank, it comes under automatically updated with output condition records
Input Screen:
Output Screen:
Regards,
Ganesh Padala
Answer:
We can get the program details of a single Transaction code with the help of Transaction Code SE93. But if we need the programs of multiple Transaction codes, we can use table TSTC to get the same. You can find below screen shots which will provide respective details.
This table can be used to get the details of Transaction codes from a Program also
Input Screen:
Output Screen:
Regards,
Ganesh Padala
