2013-03-13 - 5834.200 - Spec - Consolidated Invoices - Billing Documents #Billing #ABAPFORMS #invoices

SPECIFICATIONS

5834.200 - Spec - Consolidated Invoices

Purpose

Provide a solution for consolidated invoices to meet vendor compliance requests for Mexico, Russia and Canada.

Admin Info

Purpose
 Design a solution for consolidated invoices.
Requested By
 Thi Tran
Spec Created By
 Surya Basa/Sandeep Gurram
Spec Created Date
 03/13/2013
Spec QA by
 Surya Basa
Objects
 RV60C601
V_TVCPFL
VVC_T682_V2
ZZKUNAG_CUSTOM
ZISD_ETI_INVOICE_EXTRACT
Document Status
 Complete
NB: This is a global solution and is not specific to Mexico, Russia or Canada. It may be used at the discretion of the business locally/globally.

References

Prior Tickets

None

Documents

Consolidated Invoices.xlsx


Functional Requirement


Define a solution to consolidate invoices to meet vendor compliance requests for Mexico, Russia and Canada.
Currently, each delivery gets its own invoice. This sometimes results in multiple invoices sent to a customer on a daily basis. This project will consolidate deliveries onto fewer invoices, which will reduce customer charge backs and reduce the amount of processing by the customers, potentially decreasing the time it takes for us to be paid. Multiple delivery documents should be consolidated

The nightly billing batch job should consolidate invoices for any order type that is being billed that day. Therefore, delivery related orders, if shipped on the same day, should all get processed and consolidated together in the nightly job or if created manually in Billing Due.

To update customer grp 3 attribute at header level and Sales order,delivery number at item level in the Mexico SD ETI file.

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]

The solution involves developing a custom routine (601) and specifying the criteria for consolidation of invoices. The following are the criteria for consolidation of delivery based documents for Order Types - ZOR and ZPTO -
1. Customer should be marked for consolidation in the cusotmer master - Customer Attribute 3.
2. Sold to party and Ship to party in the delivery documents should be the same.
3. PO number on the sales documents must be the same.
4. Actual Goods Issue Date must be the same on the documents meant for consolidation.

For Mexico
Add a new key combination to maintain condition records for output ZINV for customers not needing consolidation of invoices.

Test Plan

[List test scenarios/cases to be executed here]
Scenario
 Expected Result
Create invoices via VF04 for multiple deliveries (item catergory TAN/TAB) with same SP, SH, PO number and customer
marked for consolidation in Customer Attr3.
 F2 invoices should be consolidated.
Create invoices via VF04 for multiple deliveries (item catergory TAN/TAB) with same SP, SH, PO number and customer
not marked for consolidation in Customer Attr3.
 F2 invoices should not be consolidated.
Create invoices via VF04 for multiple deliveries (item catergory TAN/TAB) with same SP, SH, different PO number and
customer marked for consolidation in Customer Attr3.
 F2 invoices should not be consolidated.
Create invoices via VF04 for multiple deliveries (item catergory TAN/TAB) with same SP, different SH, samePO number and
customer marked for consolidation in Customer Attr3.
 F2 invoices should not be consolidated.
Create invoices via VF04 for multiple deliveries (item catergory TAN/TAB) with different SP, same SH, PO number and
customer not marked for consolidation in Customer Attr3.
 F2 invoices should not be consolidated.
Create invoices via VF04 for multiple deliveries (item catergory TAN/TAB) with same SP, SH, PO Number and customer
marked for consolidation in Customer Attr3; with plants involvng two company codes.
 F2 invoices should be consolidated and separate ICO
documents should be created.
Create invoices via VF04 for multiple deliveries (item catergory TAN/TAB) with same SP, SH, PO Number and customer
marked for consolidation in Customer Attr3; with plants involving two and three company codes.
 F2 invoices should be consolidated for separately for documents
with two company codes and three company codes and individual
ICO documents should be created.
Create invoices via VF04 for multiple deliveries (item category TAN) with same SP, SH, PO Number and customer marked
for consolidation in Customer Attr3; Customer from sales Org 1500 - Mexico and output condition record maintained for ZINV
output type with the key - Sales Org/Delivery Type/Ship to and Dispatch time 1.
 F2 invoices should be consolidated and ZINV output should not be
triggered on Goods Issue.
For Mexico (sales Org - 1500):
Create two deliveries for customer 1010440 (marked for consolidation) with same SH, PO Number, GI date;
One delivery with same SH, different PO number, same GI date; and
One delivery for customer 1010446 (not marked for consolidation) with same SH, PO Number and GI date;
Maintain condition record for ZINV output with key Sales Org/Del Type/Sold-to for customer 1010446
 F2 invoices should be consolidated for the two deliveries with SP-1010440 having
same SH, PO Number, GI date
F2 individual invoice should be created for delivery with SP-1010440 having
different PO Number.
F2 individual invoice should be created on PGI for the delivery with SP-1010446;

Test Scenario
 Expected Result
Create a consolidated invoice with customer 1010400 with customer attribute marked as X.Trigger ZETI output in the invoice and check the file.
 The customer attribute 3 field should be populated with X value and delivery number should be displayed as MULTIPLE at header level.
At item level the Sales order and delivery number should be displayed beside the corresponding item.
Create a standard invoice with customer 1010400 with customer attribute marked as X.Trigger ZETI output in the invoice and check the file.
 The customer attribute 3 field should be populated with X value at header level.
At item level the Sales order and delivery number should be displayed beside the corresponding item.
Create a standard invoice with customer 1010409 with customer attribute marked as blank.Trigger ZETI output in the invoice and check the file.
 The customer attribute 3 field should be populated as blank value at header level.
At item level the Sales order and delivery number should be displayed beside the corresponding item.

Solution Details

[Provide complete technical details for configuration or programming here]

1. Update the copy controls in VTFL for TAB item category for F2-LF combination to include routine 601.


2. Modify the Long, Medium, Short descriptions of field(KATR3) accordingly so as the field gets identified that is for Consolidation.
3. Create new entries in table(TVK3) with 'X' and ' ', As these field entries is set for customer based on which logic should trigger for consolidation.
4. Modify the routine 'RV60C601' to fill the field VBRK-ZUKRI, if the Sold-To's customer attribute 3(KATR3) field is checked i.e 'X' fill the ZUKRI field with data of PO Number(VBAK-BSTNK), Ship-To(LIKP-KUNNR), Sold-To(LIKP-KUNAG), Actual Goods Movement Date(LIKP-WADAT_IST) as this is the base field for consolidation.
For Mexico
The Table - 603 with key combination - Sales Orgnisation/Delivery Type/Sold-To was added to the access seqeunce Z001 with requirement 3.
Condition records has to be maintained for customers not needing consolidation of invoices with the above key.

Z001.jpg

To update customer grp 3 attribute at header level and Sales order,delivery number at item level in the Mexico SD ETI file:

1.In program ZISD_ETI_INVOICE_EXTRACT we added new logic to display cutomer attribute 3 (KATR3) at header level for the consolidated customer.When the customer is not consolidated the cust.attribute field (KATR3) is displayed as blank.
2.When the invoice is consolidated the delivery number field (LIPS-VBELN) is displayed as MULTIPLE at header level.
3.Added the sales order (VBRP-AUBEL) and delivery number (VBRP - AGBEL) is printed at corresponding item at item level.

Issues

1. While maintaining condition records for ZINV condition using the key- Sales org/Del Type/Sold -to pt, the Sold to party name is not appearing in the description. This bug is caused for the custom field-ZZKUNAG created earlier for Sold-to party.
ZINV.jpg
The bug has been fixed in the Include MV13BKOM by adding the implicit enhancement to pull the name of sold to party.
ZINV-1.jpg

2. 'Multiple' is being sent out in the ETI file to EDICOM when multiple deliveries are created against an order even though the customer is not flagged for customer attribute 3 - KATR3.
The bug is caused by the code in the program ZISD_ETI_INVOICE_EXTRACT. The bug has been fixed by making the necessary code changes and tested in NED.

NB: This bug is fixed in ReCAP 8158 - Consolidated EDICOM Extract Error