2013-09-25 - 8729.100 - Spec - Carrier Determination if SO Updated #Shipping #ABAP
SPECIFICATIONS
8729.100 - Spec - Carrier Determination if SO Updated
Purpose
Enhance the
carrier determination logic by considering values from
sales order while creating the delivery.
Admin Info
Purpose
|
Determine carrier and incoterms from sales order when updated
|
Requested By
|
Daniel Brennan
|
Spec Created By
|
Surya Basa
|
Spec Created Date
|
09/27/2013
|
Spec QA by
|
Surya Basa
|
Objects
|
MV50AFZ1
ZSD_DELIVERY_DEL_TEXT
|
Document Status
|
Complete
|
References
Prior Tickets
2012-09-08 - 4580 - Spec - Logistics Enhancement - Carrier Determination
Documents
None
Functional Requirement
Enhance logistic functionality to create the delivery document if changes in sales order with new incoterms irrespective of a valid record in the carrier table. Here
the carrier determination logic is overriding the valid records from the carrier table.
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
The appropriate code changes are to made to create
deliveries by considering the Incoterms and Customer Group2 values from the sales order when they are changed even if there's a matching record in the carrier table.
Test Plan
[List test scenarios/cases to be executed here]
Test scenarios specific to functional requirement:
Sl
|
Test Scenarios
|
Expected Results
|
1
|
Create delivery for a vendor in the table with a valid record but while creating the sales order manually change the incoterms and carrier which are different from table entries and create the delivery.
|
Delivery should be created with the changed value of incoterms and carrier from the sales order. And sales order should not be updated with the table value.
|
2
|
Create Delivery for a vendor in the table with a valid record and after creation of delivery document, delete the delivery document and make change in sales order and again create new delivery.
|
New delivery should be updated with the changed value from the sales order.
|
3
|
Create a sales order for a vendor in the table with a valid record and after creation of sales order save the sales order and then goto change mode of sales order and make change the incoterms and carrier manually in sales order and save. And create the delivery document.
|
The changed value from the sales order should flow to delivery document.
|
4
|
Create delivery for a vendor in the table with a valid record and after creation of delivery document, go to sales order again and make changes in incoterms and carrier.
|
Existing delivery document should not updated with the changed value from the sales order.
|
Generic test scenarios on carrier determination:
Sl
|
Test Scenarios
|
Expected Results
|
1
|
Create Delivery for a vendor in the table with a valid record, make sure incoterms and carrier from vendor master are different from table entries.
|
Delivery should be created and sales order updated with incoterms and carrier from table.
|
2
|
Create Delivery for a vendor in the table but without a valid record.
|
Delivery should be created with incoterms ROU and carrier 157 (Routing); SO should not be updated.
|
3
|
Create Delivery for a vendor not in the table.
|
Delivery should be created with incoterms and carrier from the sales order.
|
4
|
Create Delivery for a vendor in the table with multiple valid records.
|
Delivery should be created and SO updated with incoterms and carrier from first record in table that matches the delivery weight.
|
5
|
Create Delivery for a vendor in the table with a valid record, where Header text deletion indicator is set when language is EN
|
Delivery should be created and SO updated with incoterms and carrier from table and delivery header text for Customer Account at Carrier, Address for Carrier (1) and Address for Carrier (2) should be deleted; SO header text should not be deleted.
|
6
|
Create Delivery for a vendor in the table with a valid record, where Header text deletion indicator is not set when language is EN
|
Delivery should be created and SO updated with incoterms and carrier from table and delivery header text for Customer Account at Carrier, Address for Carrier (1) and Address for Carrier (2) should be carried over from Sales Order / Customer Text; SO header text should not be deleted.
|
7
|
Create a delivery with UOM in Kg and table entry in lbs.
|
Conversion should work correctly, choosing the correct weight range table entry
|
8
|
Create a delivery with UOM in oz. and table entry in lbs.
|
Conversion should work correctly, choosing the correct weight range table entry
|
9
|
Create a delivery with UOM in TON and table entry in Kg.
|
Conversion should work correctly, choosing the correct weight range table entry
|
10
|
Create a delivery with a weight of 100 lbs when there are records for 0 - 100 and 100 - 999999
|
Delivery should be created with the incoterms and carrier from the 0 - 100 record
|
11
|
Create a delivery with weight of 101 lbs when there are records for 0 - 100 and 100 - 999999
|
Delivery should be created with the incoterms and carrier from the 100 – 999999 record
|
12
|
Create Delivery for a vendor in the table with a valid record, where Header text deletion indicator is set when language is not EN
|
Delivery should be created and SO updated with incoterms and carrier from table and delivery header text for Customer Account at Carrier, Address for Carrier (1) and Address for Carrier (2) is deleted; SO header text should not be deleted.
|
13
|
Create Delivery for a vendor in the table with a valid record, where Header text deletion indicator is not set when language is not EN
|
Delivery should be created and SO updated with incoterms and carrier from table and delivery header text for Customer Account at Carrier, Address for Carrier (1) and Address for Carrier (2) is carried over from Sales Order / Customer Text; SO header text should not be deleted.
|
14
|
Create a delivery with a weight of 100 lbs when there are records for 0 - 100 and 100 – 999999(both in KG and LB)
0-100—KG and 0-100- LB records are maintained in the table.
|
Delivery should be created and SO updated with incoterms and the Customer group 2 of the first matching entry from the table.
|
15
|
Create deliveries via batch to make sure they create correctly
|
Deliveries should be created via a batch job with the correct incoterms and carrier based on the table entries and SO's should be updated accordingly.
|
Solution Details
[Provide complete technical details for configuration or programming here]
After manually
changing defaulted values
(incoterms and Customer Group2
) at sales
order, it will update to corresponding delivery with the same value from sales order.
If KNVV-INCO1 is not equal to VBAK-INCO1
then pass VBAK-INCO1 field to LIKP.
If KNVV-KVGR2 is not equal to VBAK-KVGR2
then pass VBAK-KVGR2 field to LIPS.
Issues
None