Combine selected Debit memo request Items into one invoice

Hi
The requirment is to select line items from multi debit memo request documents and combine those line items into one invoice.
So far, our ABAP developer is designing an selection screen to list all the line items met certain criteria (e.g. certain material number, or certain service rendered dates etc.) from multi debit memo request.
My challenge is how actually combine all these line items and push into one invoice ?
I see that in VF01 SAP provides the capability to combine multi sales documents into one invoice processing . ( forget about the invoice split rule for now.) , but the item selection is greyed out.
If I use VF06 do the collective billing, where to enter the line items ?
Is there some user exit / BAPI can push line items from different sales document into one invoice creation ?
Please let me know if my requirement is not clear.
Thanks
Edited by: Eric Y on Aug 25, 2008 6:04 AM

Reply to R.Janakiraman:
1.) As my understanding that debit memo is a billing invoice. Debit Memo Request is a sales doc. At least what I meant here debit memo and billing invoice is the same document.
2.) We would like create the debit memo (invoice) through "SD" not FI.
The challenge still exists, let me explain.
Let's say we have 50 Debit Memo Request (DMR) Documents ready to bill the customer and each DMR has multi line items.
e.g. DMR 001 has 20 line items and DMR 002 has 30 line items.
The customer would like to take the 10 line items from DMR 001 and 20 line items from DMR 002 ( by certain selection criteria) to combine into one invoice.
I was thinking use VF01 to combine the DMR 001 and 002 and let the program put billing block on those non-billed items, but in reality it doens't work; because some of the line items in the original DMR may have already been blocked the user. If the program put billing block, I can't tell whether the line item billing block is set originally by end user or the program.
What I am trying to search for is the solution to take some of the line items from different DMRs and combine into one invoice, not combine several DMRs into one single invoice.
Please help if there is any BAPI can do the job .
Thank you, Ashish Mohapatra , I will ask our ABAP developer to investigate the bapi
BAPI_SALESDOCU_CREATEFROMDATA1.
SNavaneetha
You said that "The line items being greyed out is due to the property of the Item category of the DMR". Does that mean I can config the item category to allow to be entered ? Which field in the Item category that I can do that ?
Great thanks for all
Edited by: Eric Y on Aug 30, 2008 7:13 PM

Similar Messages

How to avoid more than one debit memo request referenced to an invoice

Hello Experts,
Please if you have answer to the following question let me know it, the case is the following:
I can create a debit memo request with reference to an invoice more than once time, which means I can have many debit memos request with whole reference to the same invoice number. How can I avoid it or notify to the user while creating a debit memo request that an invoice number has already a created debit memo request.
I already check the requirement and transfer routines in copy control but I cannot use table VBFA to verify if there is a previous debit memo request, and also I verify the configuration of the debit memo request.
Thanks a lot for your help.
Best Regards

Hello,
You're saying that you cannot check VBFA for previous Debit Memo Requests - is this because the previous Debit Memo Requests do not appear in the invoice's document flow? If so, please check Copying Control: Billing Document to Sales Document (item) - is the Update document flow box checked?
Regards,
Joã

Technical objects into Debit memo request

Hello all,
we want to link the Debit memo request to the equipments. We sell configurable materials with serial number (equipment).
Afterwards, we make debit memo request for some components of this equipment and we want to have the complete history into the equipment.
I have think that into debit memo request, i can go to item "techincal object" and there, to put the serial number of the original configurable material.
Which is the theoric explanation of this technical object using?.

unsolved

Cannot combine sales order item into one DN cause LC exchange rate differ

Our users want to combine all items into one DN(delivery notice) to save their effort on packing.
But it is not possible because some items were added(modified) into the sales order afterward and resulted in a situation where Exchange rate for letter-of-credit procg in foreign trade(vbkd-akkur) is changed. Which makes inconsistency between Header's vbkd-akkur & items' vbkd-akkur.
Is there any way to bypass this limitation and let those items combine into one DN?
Edited by: Chih-Chieh Chan on Dec 10, 2008 9:56 AM

Yes, all items share the same pricing date.
BTW, it made me wonder that (color:red)VBKD-AKKUR is something to do with exchange rate. I used TCode ob08 to check out all of the exchange rate users maintained. To my surprise, all exchange rate records exist no such identical value as shown in VBKD-AKKUR where that Sales Order number is under my concern. That's odd.

Debit Memo Request Issue

Dear friends,
The copy controls are set for a) Sales Order to Debit memo request (VTAA) & b) Billing to Debit Memo Request (VTAF)
Scenario #1. Sales Order Qty is 10 No (Delivery and Billing done for 10 Nos) and I have created a DMR for qty 5 Nos with reference to the sales order and created the Debit Memo.
Now when I create one more DMR with reference to the same sales order, the qty referenced in the DMR is 15 No
Scenario #2. Sales Order Qty is 10 No (Delivery and Billing done for 10 Nos) and I have created a DMR for qty 5 Nos with reference to the Billing doc and created the Debit Memo.
Now when I create one more DMR with reference to the same Billing doc, the qty referenced in the DMR is 10 No
1. While creating a Credit Memo Request or Debit Memo request whats the standard reference document to be used? Is it Sales order or a Billing doc?
2. I have tested this using standard doc types and I think this is not the correct behaviour.
In both the scenarios, the referenced qty should be 5No when you are creating the DMR for the second time.
Somebody let me know what should be the Ideal way to do it......
Thanks
Isaac

Hi Isaac,
In transaction code VTAA goto OR to DR and look for your Item Category and in that there is a field by name Pos./neg. quantity
and in that you will find the help details as shown below:
The below details will help you for all the documents like Quotatio, Sales Order , billing etc.
Quantity is calculated positively, negatively or not at all
Indicates whether, during copying, the quantity or value in the target
     document has a negative effect, positive effect, or no effect at all on
     the quantity still to be completed in the source document.
Use
The system uses this indicator to determine how the quantity in the
     source document is affected. For example, if you
o   Create a quotation item for 100 pieces,
o   Copy the quotation into a sales order, and
o   Create a sales order item for 80 pieces,
the copying has a positive effect on the quotation. In effect, you have
     added 80 pieces to the quotation quantity that is now considered
     complete. 20 pieces in the quotation remain to be completed.
If you do not make an entry in this field, or set indicator 0, the
source document is not blocked, which allows you to create several
target documents at once (for example, when using EDI and frequent
contract releases).
While the source document (such as quotation or quantity contract) is
being processed, it is blocked. For instance, if you are working on a
quantity contract, no one can create a release order for that contract).
                                                                                In sales documents, for example, you can expect the following results:
o   Quotation   -> Sales order: positive
o   Contract    -> Return: negative
o   Sales order -> Sales order: no effect
In billing documents, for example, you can expect the following results:
o   Delivery    -> Invoice: positive
o   Delivery    -> Cancellation: negative
o   Delivery    -> Pro-forma invoice: no effect
Regards

Credit/debit memo request

hi,
1) credit memo request - After create invoice in vf01, then if credit memo needed, must create credit memo request in va01 then only can create credit memo in fb75?
2) debit memo request - After create invoice in vf01, then if debit memo
needed, must create debit memo request in va01 then only can create debit memo in fb70?
3) credit/debit memo can only be created after credit/debit memo request is created?
4) if credit/debit memo not created in fb75/fb70, where in sd can create?
5) credit/debit memo request done via which tcode if not va01.
thanks

Hi Eliana,
1. A transaction that reduces Amounts Receivable from a customer is a credit memo. For eg. The customer could return damaged goods. A debit memo is a transaction that reduces Amounts Payable to a vendor because, you send damaged goods back to your vendor.
2. Credit memo request is a sales document used in complaints processing to request a credit memo for a customer. If the price calculated for the customer is too high, for example, because the wrong scale prices were used or a discount was forgotten, you can create a credit memo request. The credit memo request is blocked for further processing so that it can be checked. If the request is approved, you can remove the block. The system uses the credit memo request to create a credit memo.
You can use credit memos in Sales and Distribution (SD) for assigning credit memo requests to the open invoices and in Financial Accounting (FI) for assigning credit memos and payments to the open invoices and carry out clearing with them. If you use both Financial Accounting (FI) and Sales and Distribution (SD), there is a 1:1 relationship between the credit memo request and the credit memo item posted in Financial Accounting (FI). As soon as you bill the credit memo request together with other sales orders, or distribute the items of one credit memo request to several billing documents, the assignment is no longer valid and the system will not process it.
For credit memos, credit memo requests, and payments, you have the following assignment options:
- Assignment to a single invoice
- Assignment of a partial amount to an invoice
- Assignment to several invoices
When you post credit memos, the payment programme processes them automatically. If the credit memo is specifically related to a particular open invoice item, the payment program automatically attempts to offset the credit memo against the open item. If it is not possible to completely offset the credit memo against an invoice, you can post a debit memo to the vendor, who is to reimburse the amount. Then you can apply a multilevel dunning program.
3. Debit memo request is a sales document used in complaints processing to request a debit memo for a customer. If the prices calculated for the customer were too low, for example, calculated with the wrong scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can be checked. When it has been approved, you can remove the block. It is like a standard order. The system uses the debit memo request to create a debit memo.
4. As mentioned above, creating a credit or debit memo request enables you to create credit or debit memos based on a complaint. For this first create a sales document with the order type for a credit or debit memo request. You can create the debit or credit memo requests in the following ways:
Without reference to an order
With reference to an existing order
Here you enter which order the complaint refers to.
With reference to an invoice
Here you enter which invoice the complaint refers to.
In all cases, you specify the value or quantity that should be in the credit or debit memo
5. You can block the credit or debit memo request from being billed in Customizing. Go to Sales -> Sales Documents -> Sales document header -> Define sales document type and select the billing block field in the billing section. This request can later be reviewed along with similar ones, - if necessary, by another department. The request for a credit or debit memo can then be approved or rejected.
Credit memo and debit memo is created used the T.Code VF01, in which we have to choose the billing type as Credit Memo or Debit Memo.
Credit Memo Request or Debit Memo request are created using T.Code VA01, in which we have to select document type as G2 or L2.
Hope this gives you some idea.
REWARD IF HELPFUL.
Regards,
Praveen

Debit Memo Request

Hi !
I am trying to configure Debit Memo Request. Can anybody tell me the same?
Rgds,
Indrajit

Debit Memo Request:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:DR is the sales document type for Debit Memo Request. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Step 2:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: L2 is standard Billing Type for Debit Memo. If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing.
Note: Ensure that Copy Control settings are done
Sales Order to Billing (OR --> F1): VTFA
Regards,
Rajesh Banka
Reward point if useful.

BAPIs to create sales orders for Returns and Debit Memo Request

Hi,
I have to create a sales order for document type Returns as well as a debit memo request.The BAPI 'BAPI_SALESORDER_CREATEFROMDAT2' is giving the following error message for Debit Memo Request document creation as well as for Returns.
761 Unpermitted combination of business object BUS2032 and sales doc. category L
I found BAPIs:
BAPI_CUSTOMERRETURN_CREATE for creating sales document of type ZDRE and SD document category H.
BAPI_DEBITREQUEST_PROXY_CREATE for creating sales document of type ZDDR and SD document category L.
please let me know if anybody have used them. If so what values need to be passed to I_UPLOAD_ID,I_DESTIN,I_SFA_REL parameters of BAPI_DEBITREQUEST_PROXY_CREATE. Are there any alternative solutions using the Salesorder bapi.
I have to create documents based on the flat file data no reference sales document numbers are available.
Appreciate your help..
Good Day
Regards
Bhargavi

Look at the code done by me
Program Name:                                                        *
SAP Name    : ZAXXXXXX               Version    :                    *
Programmer : Chris Dong of ITDC                    *
Description :                                                        *
Includes        :                                                    *
Function Modules: XX_XXXXXX                                          *
Transactions    :                                                    *
Programs        :                                                    *
REPORT XXXXXXXX LINE-SIZE 80
                 LINE-COUNT 65
                 MESSAGE-ID ZA
                 NO STANDARD PAGE HEADING.
CLEAR l_order_partners.
l_order_partners-partn_role = 'AG'.
l_order_partners-partn_numb = '0001202491'.
APPEND l_order_partners TO li_order_partners.
CLEAR l_order_partners.
l_order_partners-partn_role = 'WE'.
l_order_partners-partn_numb = '0001202491'.
APPEND l_order_partners TO li_order_partners.
Sales document type
l_order_header_in-doc_type = 'ZDR'.
Sales organization
l_order_header_in-sales_org = '1000'.
Distribution channel
l_order_header_in-distr_chan = '01'.
Division
l_order_header_in-division = '04'.
REF DOCUMENT
l_order_header_in-REF_DOC = '9100000144'.
order reason
l_order_header_in-ord_reason = '925'.
item number
l_order_items_in-itm_number = '000001'.
material no
l_order_items_in-material = '000000000007000012'.
Qty
l_order_items_in-target_qty = '0000000000100.000'.
APPEND l_order_items_in TO li_order_items_in.
*BUS2094 Credit memo request " OSS NOTE 93091
*BUS2096 Debit memo request " OSS NOTE 93091
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA'
EXPORTING
ORDER_HEADER_IN = l_order_header_in
BUSINESS_OBJECT = 'BUS2096'
WITHOUT_COMMIT = ' '
CONVERT_PARVW_AUART = ' '
IMPORTING
SALESDOCUMENT = l_vbeln
RETURN = li_return
TABLES
ORDER_ITEMS_IN = li_order_items_in
ORDER_PARTNERS = li_order_partners
Message was edited by:
        Chris Dong
null

Issue related to Debit Memo Request

hello,
I am facing one issue related to debit memo request,as when i generating Debit memo request through DP90 t code,in debit memo request whatever the line items it will generate through this t code it all are getting in to NON-EDITABLE MODE,so i need to make this in to EDITABLE MODE, i have change in the condition types as "MANUAL" even though its getting in to non editable mode ,so please help me to make this line items in to editable mode.

Hi Abdul,
We have a provision in DP90 itself to change the price of the conditions, if manual changes are allowed to the conditions. Please check the configuration setup of the condition type whether manual changes are permitted or not.
Regards,
SAM

Plant Replication CRM Service Contracts & Orders - ECC Debit Memo Requests

Dear experts
we are struggling with the assignment of a plant in SAP ECC Debit Memo Request Line Items created from SAP CRM documents - the Plant field on the Shipping tab stays empty. This refers to Service Products.
We use CRM 7.0 (however, same problem exists in 2007) with ECC 6.0 with the following main relevant settings:
- Service Products do not have a Plant assigned in their Distribution Chain data
- Table CRMC_SEORG_R3MNP contains a correct mapping of service organizations to plants
- Table OFIC_PLANT_SVC does not contain relevant settings, as we assume this table as not relevant in this scenario
This is the end status after some trial&error sessions - we did not find a successful combination of settings amongst the above.
Thanks in advance & kind regards
Christian

Should it be a problem related to the leading zeros?

Debit memo request with reference to the credit memo request

Dear SD Consultants,
I have a business scenario in which I create a credit memo request with reference to a debit memo request but the problem is that ,i can create many debit memo requests with reference to the same credit memo request even if the all target quantity was referenced , I still can create many debit memo requests with reference to the credit memo request so can any one tell me how to restrict creating debit memo request with reference to the credit memo request up till the all target quantity was referenced.
Regards,
SD Consultant

Dear Saju.S,
I have checked all the positive/negative values in the item copy control but none of the values works as i still can create many debit memo requests with reference to the credit memo request.
Regards,
Sd Consultant

Creating a debit memo request with reference to an invoice

Hi,
An invoice shows wrong MWST value because of incorrect customer tax classification as Tax exempt. I corrected the cust tax classification to "Liable for Tax". Then I tried to create a debit memo request with reference to the incorrect invoice. Thats a requirement by the customer. Invoices with incorrect VAT are not to be cancelled. A specially created VAT only sales order (Debit memo request) is used to create a sales order with 0 net value and correct MWST . But while trying to create the debit memo request, the system picks up the same old condition record for the MWST. How to overcome this situation ?
The copy control for the item category from billing doc to debit memo request is set to "B" that is new pricing. I even tried to update pricing. But it does not work. Changing the Service rendered date or the pricing date to current date also does not help.
Please help.
Regards.

This is working fine. What I did was
1: create a new pricing procedure
2: made the PR00 condition statistical
3: using a routine calculate the MWST based on the PR00. But PR00 itself does not contribute to the net value. This part is working fine. I could create debit memos successfully.
The problem is if we change either the customer or the material tax classification after creating the invoice, and then create a debit request with reference to the incorrect invoice, the system still considers the old tax classfication and therefore the old MWST rate. If I create a debit request without reference, the new rate is applicable.
I hope I have made clear.
Regards.

Cancel of debit Memo, Don't want debit memo request in VF04

Senario:
1.Cerated debit memo request.
2. Created debit memo and passed to accounting.
3.Cancelled debit memo and passed to accounting.
4. Debit memo request is in open status and appears in VF04.
Now what I done is I applied reason of rejection to item in debit memo request to make the status complete--> Not happened.
Tried to delete the debit memo request but received Information: Not able to delete the document as subsequent document is present.
Kindly help.
Hrishikesh

Hi Friends,
I did manage to remove the debit memo request from VF04 and for that I did following things the debit memo request:-
1. Added Item Usage in DMR (debit memo request)
2. Added Reason for rejection
3. Added order reason
Hope this will help you all if you face simillar kind of problem.
Regards,
Hrishi

Not able to edit the Debit memo request after cancelling Billing document

Hi,
This is a process in SD/Customer service.The issue is even after cancelling the billing document we are not able to edit the item details in debit memo request..Pls suggest how we can edit the item details after cancelling the billing document
Best Regards
Jay

Hi Jay,
Yes, the whole sales document could not be deleted as well.
Sorry for the misleading answer.
As per the long text of error V1006, the document cannot be completely
deleted because further processing has already taken place. Even though
you have cancelled the subsequent documents, if you refer to the
document flow, the subsequent documents might have already been created
The cancellation of these does not delete the request.
Please have a look at table VBFA in transaction SE16 and you can see
that the subsequence documents are still displayed.
What you can do is to enter a reason of rejection for all items to
prevent further processing of the request.
Please refer to Note 147028, you don't need to apply
this note, please refer to part of "NOTE:...".This is a restriction
of the system.
For order-related billing, it is not possible to delete the sales
document, even if the subsequent invoice has been cancelled.
You have to reject the items.
Cheers,
Alex

Copy Control from Billing doc to Debit memo request

hi,
we are trying to sort the follwing problem out. We create a debit memo request with reference to the invoice, we then change the sold to party, however the pricing is carried out again. we want to retain the invoice values but only change the sold to party and quantities. i have change the copy control to "copy pricing elements unchanged" however it still reprices the debit memo.

Hi,
As per your question, You have invoiced customer X wants to issue debit memo request to customer Y.
How come is it possible?Could you elaborate the scenario?
SAP system retrieve master data from sold -to-party record for Sales order and also access ship-to-party record for delivery and access Payer's record for Billing.
You change sold to party in Debit memo request.SAP system access record of new sold-to-party for debit memo req.(It is sales order type).
In T-code VTAF - You changed Pricing type to D-copy pricing elements unchanged.It is not sufficient to fulfill your requirement.In this transaction other Data transfer routine also affects copying.These are Data transfer routine 104(business data item billing) and 004(Billing item partner).
Data transfer routine allow you to fine tune the transferred fields during the copying process.It specifies the item business data to be transferred from a billing document item to a sales document item.Special checks are also performed to be sure that SOLD -TO-PARTY IS THE SAME PRIOR TO initiating data transfer of the item related business data.Iten related business data are incoterms,taxes discount applicable to Sold-to-party.
In your case sold-to- party is changed.It also changes business data and pricing.
Hope it would help you.
Thanks,
Vrajesh

Combine selected Debit memo request Items into one invoice

Similar Messages

Maybe you are looking for