Thursday, January 31, 2019
Wednesday, January 30, 2019
Tuesday, January 29, 2019
Question no 3619 : IE4N
In SAP PM as at ECC6.0 EhP6, which of the following processes are possible via IE4N ?
(more than one answers)
A) Goods Issue.
B) Goods Receipt.
C) Installation.
D) Dismantle.
E) Swap.
.
Answer: A, B, C, D, E
All of the above.
(more than one answers)
A) Goods Issue.
B) Goods Receipt.
C) Installation.
D) Dismantle.
E) Swap.
.
Answer: A, B, C, D, E
All of the above.
Sunday, January 27, 2019
Question no 3618 : MIGO
In SAP MM as at ECC6.0 EhP6, MIGO can be used to perform which of the following functions ?
(more than one answers)
A) Goods Receipt.
B) Cancel Goods Movement.
C) Subsequent Delivery.
D) Goods Return to Vendor.
E) Subcontracting Adjustment.
.
Answer: A, B, C, D, E
Access MIGO and view the Activities drop down list.
(more than one answers)
A) Goods Receipt.
B) Cancel Goods Movement.
C) Subsequent Delivery.
D) Goods Return to Vendor.
E) Subcontracting Adjustment.
.
Answer: A, B, C, D, E
Access MIGO and view the Activities drop down list.
Saturday, January 26, 2019
Friday, January 25, 2019
Question no 3617 : Vendor Master Purchasing data structure
In SAP MM as at ECC6.0 EhP6, which of the following data structure level can be created for the Vendor Master Purchasing Data view ?
(more than one answers)
A) Plant.
B) Purchasing Organization.
C) Purchasing Group.
D) Sub-Range.
E) Company Code.
.
Answer: A, B, D
The Vendor Group for creating the Vendor Master can be activated to create the Vendor Master Purchasing Data view at Plant and Sub-Range level.
(more than one answers)
A) Plant.
B) Purchasing Organization.
C) Purchasing Group.
D) Sub-Range.
E) Company Code.
.
Answer: A, B, D
The Vendor Group for creating the Vendor Master can be activated to create the Vendor Master Purchasing Data view at Plant and Sub-Range level.
Thursday, January 24, 2019
Wednesday, January 23, 2019
Question no 3616 : Goods Receipt for Purchasing Document
In SAP MM as at ECC6.0 EhP6, Goods Receipt cannot be performed for which of the following Purchasing Document ?
(more than one answers)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: C, E
You can only GR to PO and SA.
(more than one answers)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: C, E
You can only GR to PO and SA.
Monday, January 21, 2019
Saturday, January 19, 2019
Question no 3615 : Message Determination in MM Purchasing Document
In SAP MM as at ECC6.0 EhP6, which of the following Purchasing Document do not result in Message Determination ?
(only one answer)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: A
PR is an internal document without Header and also without Message Output. Unlike PO, RFQ, Contract or Scheduling Agreement which have Headers and also Message Output for sending official requirements to the Supplier.
(only one answer)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: A
PR is an internal document without Header and also without Message Output. Unlike PO, RFQ, Contract or Scheduling Agreement which have Headers and also Message Output for sending official requirements to the Supplier.
Thursday, January 17, 2019
Question no 3614 : Item Category and Account Assignment in Purchasing Document
In SAP MM as at ECC6.0 EhP6, which of the following Purchasing Document cannot be created with both Item Category and Account Assignment ?
(only one answer)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: B
RFQ do not have the field Account Assignment. This is because Account Assignment is only for internal information and postings and not required for RFQ that is swnd to the supplier. When a Purchase Requisition is raised with Account Assignment and converted to an RFQ, thr Account Assignment information from the PR is not copied to the RFQ.
(only one answer)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: B
RFQ do not have the field Account Assignment. This is because Account Assignment is only for internal information and postings and not required for RFQ that is swnd to the supplier. When a Purchase Requisition is raised with Account Assignment and converted to an RFQ, thr Account Assignment information from the PR is not copied to the RFQ.
Wednesday, January 16, 2019
Tuesday, January 15, 2019
Monday, January 14, 2019
Saturday, January 12, 2019
Question no 3613 : Purchasing Document with a Valid Period
In SAP MM as at ECC6.0 EhP6, which of the following Purchasing Document can be created with a Validity Period ?
(more than one answers)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: C, D, E
A) A Purchase Requisition does not have a header (where validity periods in the PO and Outline agreements are stored), at the moment document item levels do not have validity periods.
B) Have not tested RFQ header validity period but business wise, we would only required the expected delivery date for the item requested as RFQ to the vendor and the vendor would provide the Quotation stating both the price and validity periods for the evaluations. At that point, then the Quotation to be generated to Outline Agreements will carry a validity period.
C) Blanket PO can have a valid Period, the valid Period fields at the PO Header are switched off using Field Selection assigned to the PO Document Type in the IMG.
D, E) Outline Agreements in MM ie: both Contract and SA have Validity Periods. The Validity periods are mandatory even on standard Outline Agreement document types provided by SAP.
(more than one answers)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: C, D, E
A) A Purchase Requisition does not have a header (where validity periods in the PO and Outline agreements are stored), at the moment document item levels do not have validity periods.
B) Have not tested RFQ header validity period but business wise, we would only required the expected delivery date for the item requested as RFQ to the vendor and the vendor would provide the Quotation stating both the price and validity periods for the evaluations. At that point, then the Quotation to be generated to Outline Agreements will carry a validity period.
C) Blanket PO can have a valid Period, the valid Period fields at the PO Header are switched off using Field Selection assigned to the PO Document Type in the IMG.
D, E) Outline Agreements in MM ie: both Contract and SA have Validity Periods. The Validity periods are mandatory even on standard Outline Agreement document types provided by SAP.
Thursday, January 10, 2019
Wednesday, January 9, 2019
Tuesday, January 8, 2019
Question no 3612 : MM Purchasing Document without a Plant
In SAP MM as at ECC6.0 EhP6, which of the following Purchasing Document can be created without a Plant ?
(more than one answers)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: B, D
Both RFQ and Contract can be created without a Plant.
(more than one answers)
A) Purchase Requisition.
B) RFQ.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.
Answer: B, D
Both RFQ and Contract can be created without a Plant.
Sunday, January 6, 2019
Saturday, January 5, 2019
Question no 3611 : Validity Periods in Material Management Master data
In SAP MM as at ECC6.0 EhP6, which of the following in MM has validity periods ?
(ore than one answers)
A) Source List.
B) Purchasing Info Record General Data.
C) Purchasing Info Record Condition Record.
D) Quota Arrangement.
E) Material Master MRP data view.
.
Answer: A, C, D
A) Goto ME01, each source list entered for a Material/Plant combination must have a valid period.
B, C) Goto ME11, the General and Purchasing Data views do not have valid period but the Condition TAB data will have valid period.
D) Goto MEQ1, the Quota Arrangement header has a valid period.
E) In General, the Material Master do not have a valid period of from-to, although you have create/change a Material with a date, and the material status entered can have a valid from date. (Hiwever, there are two related schedule change Material Master t-code MM12 and the MM13 to Activate the Changes)
In this case, you can make an argument of the answer should be A, C, D, E but I decided to be A, C, D.
(ore than one answers)
A) Source List.
B) Purchasing Info Record General Data.
C) Purchasing Info Record Condition Record.
D) Quota Arrangement.
E) Material Master MRP data view.
.
Answer: A, C, D
A) Goto ME01, each source list entered for a Material/Plant combination must have a valid period.
B, C) Goto ME11, the General and Purchasing Data views do not have valid period but the Condition TAB data will have valid period.
D) Goto MEQ1, the Quota Arrangement header has a valid period.
E) In General, the Material Master do not have a valid period of from-to, although you have create/change a Material with a date, and the material status entered can have a valid from date. (Hiwever, there are two related schedule change Material Master t-code MM12 and the MM13 to Activate the Changes)
In this case, you can make an argument of the answer should be A, C, D, E but I decided to be A, C, D.
Friday, January 4, 2019
Thursday, January 3, 2019
Wednesday, January 2, 2019
Tuesday, January 1, 2019
Question no 3610 : Material Type fucntionality
In SAP MM as at ECC6.0 EhP7, the Material Type configuration allows to define the Mterial Master for the following business processes ?
(more than one answers)
A) Pipeline processing.
B) MPN processing.
C) Consignment processing.
D) Sub-contracting processing.
E) Plant-to-Plant transfer processing.
.
Answer: A, B
Material type configuration does not provide functionality or switches for consignment, sub-contracting or plant-to-plant transfer processing in MM.
(more than one answers)
A) Pipeline processing.
B) MPN processing.
C) Consignment processing.
D) Sub-contracting processing.
E) Plant-to-Plant transfer processing.
.
Answer: A, B
Material type configuration does not provide functionality or switches for consignment, sub-contracting or plant-to-plant transfer processing in MM.