RV Doc Type

Hi,
Our sales order type are YA and YH, YA for cash sales and YH for charge sales. In case of reversal of billing document, doc type generated should be the same as the original document.
There are cases wherein reversal of YH or YA sales generated RV doc type. What could be the reason for this? RV is generated only when we use t.code VF11 for the reversal. We are now using VF02 for the cancellation/reversal of billing document.
How can we prevent RV doc type generation?
Thanks and best regards,
Rachelle

Dear Rachel
Invoice cancellation S1 is a Billing document Type whereas Document type RV is an Accounting document Type.
"Invoice Cancellation type " proposal comes from the Billing document type. You can change the proposal in the Billing document type screen in t.code VOFA, provided the relation must exist in the copy control table.
Whenever a Billing document is saved , always an Accounting document is created in FI ( except Proforma Invoice & if no Posting block).
So there are various accounting documents are available in the standard system & through these document types ,different postings are differentiated.
Normally, from F2 type of Billing document, DR type of accounting document is created.
Similarly, from Billing type G2, accounting document type DG is created.
So, you have to specify these document types in the in the billing type in VOFA, in the "Document type " field.
I mean for billing type F2, specify document type DR & for billing type G2, specify document type DG and so on.
If , you leave this field ( Document type) blank then,
it may be any billing document, System will make the posting in the Accounting document type RV.
That is what happening in your case.So do accordingly.

Similar Messages

  • KR doc type posted without vendor line item a mandatory item category

    Hello Gurus,
    We have SPL document splitter activated in our ECC system. We have the business transaction variant 0300 / Z001 assigned to doc type KR. The vendor line is obligatory in the above business transaction variant (BTV). THe splitting rule is also assigned for this BTV.
    THe problem is that despite having the vendor as obligatory for this BTV, we are able to post the doc type KR (vendor invoice) without the vendor line item e.g.. doc with doc type KR and debit and credit to expense a/c.
    Please share your experience if anyone has come across this issue,
    Prakash

    Hi,
    To make the vendor line mandatory for KR document type, you can write the validation as below:-
    Step 1:-
    Create a message ID via transaction code SE91 for message class /EACC/MSG/ACC_COMP as you want to display to user.
    Step 2:-
    Go to transaction GGB0 and create the validation step at complete document level in Financial Accounting as below:-
    Pre Requisits:-
    BKPF-BLART = 'KR'.
    Check:-
    Create a exit code using user exit and check that line items have at least one vendor line item.
    For this take the help of ABAPer and create a copy of the program RGGBR000 and code your check here and assign to the application area GBLR in view V_T80D via transaction code SM30.
    Message:-
    Message created in step 1 as error message.
    Step 3:-
    Please also check that this validation has active status (Status=1) at line complete document level (level 3) for your company code in transaction OB28.
    Regards,
    Gaurav

  • Changing doc. type after creating a doc. type.

    Hi Friends,
    We are doing our time ageing from the time of creating the document in DMS. We created a document with particular doc. type wrongly, after two days we found that the DMS creation was done with wrong doc. type. In this how to transfer to new correct doc. Type, if we delete this & create a new we canu2019t get any info that it was created two days back.
    We made Z report for this time ageing report.
    Regards,
    Sai Krishna

    You cannot change the document type after the document has been created. The only way to do this would be with an enhancement and this would create major issues with the integrity of your system

  • Billing doc types

    Hi Gurus,
    Can I confirm that invoice list is not a billing doc type and
    Returns and External transactions are also not billing doc types.
    I am not sure if only 'returns' is mentioned, does it mean the Returns order , the Returns delivery or credit memo request of that return or the credit memo for the returns.
    thanks.
    M Russo

    Yes it is true that you can consider Invoice List also as one of the billing document type.  I hope you would be aware of the functionality of Invoice List.
    For more details, go through these documentations.
    [Creating an Invoice List|http://help.sap.com/saphelp_45b/helpdata/en/dd/56111c545a11d1a7020000e829fd11/frameset.htm]
    [Invoice List|http://help.sap.com/saphelp_46c/helpdata/en/dd/561102545a11d1a7020000e829fd11/content.htm]
    thanks
    G. Lakshmipathi

  • WRP1 excluding open POs based on doc type

    Hi friends,
    We are using SAP IS Retail ECC 6.0
    In our business, we are having requirement that Open PO quantity of particular document type (eg ZNBA) should be excluded from the WRP1 requirement calculation.
    Eg:
    For an article 100001, Site A001, following are the details,
    Reorder point - 10
    Target stock - 20
    Current stock - 5
    Open PO quantity: (ZPO1 and ZPO2 are PO doc. types)
    ZPO1 - 2
    ZPO2 - 1
    Now WRP gives requirement of article as of 12 quantities.
    My requirement is to it should not include ZPO1 open quantity in consideration but should take ZPO2 into consideration.
    Hence requirement is to create PO for 14 quantities
    How do I achieve this?
    We have a control in SAP IS Retail where we can specify, that stock of which storage location should be considered in replenishment requirment calculation.
    Do we have a similar control for the PO Doc type?  If not, how do I achieve workaround?
    Thank you,
    regards,
    Gaurav

    Hi,
       Do the Following,  Create a new storage location., "ZL01"
    Whenever your creating a PO with this "ZPO1" document type assin this Slocation "ZL01", then do the below settings in SPRO..
    SPRO->Materials Management->Consumption-based Planning->Planning->Define Storage Location MRP per plant.
    (In RP indicatior please give "1"Storage location stock excluded from RP, this will exclude the stk from this location)
    Regards
    GK.
    Edited by: Gnana Kumar on Oct 22, 2010 11:15 AM

  • Creation of Excise Invoice in J1IS Transaction - using DLFC ref. doc. type

    Hi,
    I tried to create the excise Invoice using Ref. Doc Type DLFC in J1IS by giving the material document. But it is not allowing me to process further.
    The business process requirment is to create a Supplementary Excise Invoice(Customer is Billed for a lesser value earlier)
    we tried the following:
    1. Credit memo request
    2. Credit Memo
    3. Excise Invoice in J1IS using sub.Tran Type(to map the Sales exc Inv Accounts). The reson why we used J1IS is to meet the requiremnt of generating the Outgoing Excise Invoice Number which is not possible in J1IH.
    Now the issue is, the excise invoice created in J1IS is not available for Utilizaton in J2IUN
    Please Suggest what process to be followed to address the issue.
    regards,
    Girish

    In normal circumstances, it is not possible to generate an excise invoice for credit / debit notes in SAP.  Moreover, DLFC excise invoice type can be generated only if delivery is involved.  So in order to achieve the requirement (and fool the system :-|), you can try by creating a delivery with an item category as TAX so that it will not check for stock, do PGI and invoice (credit memo) can be generated  referencing credit memo request.  Finally, try to generate an excise invoice via J1IIN
    I have never tried this option and hence, its only a guess that this should work.  Update after testing.
    thanks
    G. Lakshmipathi
    Edited by: Lakshmipathi on Jul 26, 2011 2:07 PM

  • Posting of cross company transaction with different doc types

    Hi,
    The scenario is:-
    We have two companies X and Y.
    X makes a payment to Y with the following FI entries:-
    Company Code X
    Dr Vendor Y
    Cr Bank HDFC
    Company Code Y
    Dr Bank ICICI
    Cr Customer X
    Now this needs to be a cross company transaction where the doc type for CC X should be vendor Payment 'KZ' while the doc type for CC Y should be a customer reciept with doc type 'DZ'.
    Although I am able to map the accounts in cross company code config I am not able to split the transaction of different company codes with different document types.
    Is there any way we can do this in standard SAP?
    Thanks in advance,
    Nitish

    Hi
    As per your issue ...There are no possibilities to post   in sap with different document types.
    If you want you can post cross company code transactions with one document types
    Regards
    vamsi

  • How to set Goods Receipt Indicator in PO based on Vendor or PO doc type

    Hi.
    Can someone suggest any solution to automatically set the Goods Receipt Indicator in PO (ME21N) to "blank" (untick) based on either a vendor or a PO doc type.
    Thanks.
    Tess

    You can untick it from vendor master and info record.
    1. Using MK02 - Go to purchasing data and the untick the GR-based Iv
    2. In info record for the vendor and particular material - purchasing organization data1

  • FB05 - trans to be processed and first line item PK for doc type

    Hi all,
    Me quite confused of the entry for the following document type in FB05
    DG - cust credit memo
    DR - cust invoice
    SA- gl acc doc
    SB - gl acc posting
    KG - vdr credit memo
    DZ - customer payment
    Need the help to let me know for document type above, what radio button to choose in transaction to be processed and also what posting key use at first line item.
    Also if i choose the wrong transaction to be processed radio button, any impact?
    thanks
    rgds

    Document type is primarily used to distinguish different various types of transactions. Ultimately, there are only two effects in accouting - debit and credit. Thus, doc type helps distinguish btw various types of accounting entries. It also controls certain field status while document posting and also drives the number range for the accounting document.
    Posting keys determine whether a transaction will be a credit or a debit. They also have an influence over the field status of the document entry screen. Posting keys are broadly divided into those belonging to
    Customer                             - Acct type C
    Vendors                               - Acct type V
    GL                                       - Acct type G
    Fixed Assets                        - Acct type A and
    Material Mgmt. transactions   - Acct type M
    For each account type there are both debit and credit posting keys. You can clik on F4 on the posting key field and see the various entries. You will understand.
    Thus, which posting key to enter depends on the transaction you want to enter.
    Regards,

  • Integration of ECC Scheduling Agreement (Doc Type LP) with SAP TM

    Hello Experts,
    I am trying to integrate ECC Scheduling Agreement (Doc Type LP) to create OTR in TM System. I have maintained below settings:
    1. Create and Activate Control Key
    2. Output determination procedure linked to LP has output type TRS0 with requirement 27 assigned.
    3. Output condition record has been created
    4. I have checked Business Functions are also active
    I was able to transfer other Document Types like OR; RE; FD (ECC Free of Charge); SDF (ECC Subsequent Delivery - Free of Charge); Consignment Fill up and Consignment Pick up by maintaining these settings, but not able to push Scheduling Agreement LP to TM.
    The output TRS0 is not appearing automatically and if I try to insert and execute this output in Scheduling agreement, Output is failing with error message: "Order is not TM-relevant"
    Is there any other config or mapping or SAP Note that needs to be applied to achieve this integration? Because I believe standard integration is available for ECC Scheduling agreement (I have read in help.sap.com).
    Thanks and Regards,
    Vikram Bhardwaj

    Hello Vikram,
    You mean this documentation:http://help.sap.com/saphelp_tm81/helpdata/en/9c/787f3c0a771e57e10000000a114084/content.htm?frameset=/en/44/b0488e9c35612be10000000a155369/frameset.htm ?
    I think there is talking about the integration for SCM Basis as SOS, not Order Integration.
    Regards, Marcelo Lauria

  • Scheduling agreement with relase - doc type LPA with JIT

    Hi
    can any one give the steps for Scheduling agreement with relase - doc type LPA with JIT process.. and explain how the JIT will work in SA.
    Pls advise what are config required and what the user tcode needed to perform the SA with JIT concept.

    Dear Friend,
    Without release documentation(Document type LP)
    The delivery schedule lines have official character-that is to say,they are transmitted to the vendor as they are saved in the system.The system does not document in detail releases aganist the scheduling agreement that have been sent to the vendor.Therefore,in the case of the document type without release documentation,the message control facility should be set up in such a way that a message is immediately sent to vendor if any changes are made to the delivey schedule stored in the system.
    With release documnetation(Document type LPA)
    If you use scheduling agreement with release documentation,the delivery schedule lines are not transmitted directly to the vendor.Intially ,the lines of the delivery schedule stored in the system for an LPA scheduling agreement for an internal information only.A message informing the vendor of your material requirements cannot be transmitted to the vendor until you explicitly create an SA release,that is forecast (FRC) or Just in Time(JIT) delivey schedule.Through this process,you can change the way schedule lines are represented.With release documentation,you can disply the SA releases(delivery schedules) transmitted to a vendor over a certain period of any time.This enables you to trace precisely when you sent which information to vendor.
    Regards
    Pramod

  • Delete a line item from Sales Doc type RE

    Unable to delete a line item from a sales order linked to document type RE.  Get a long runtime - no specific error message.  Use the 'Stop Transaction' option to end the transaction.
    Have done thorough testing and can delete line items linked to all other sales document types in our system.
    Researched SPRO to see if there was a line item deletion option that was not created for sales doc type RE - but can find nothing.
    On a critical time line here - this was discovered during Hotpak installation testing which is scheduled to move to PRD June 22.  Question as to why we have not run across this issue before now??  - I don't think we have had an occasion to delete a returns line item before - but I want to have the option if available.
    Any help to resolve this issue would be appreciated.
    Regards
    Patsy

    Thanks for your response.
    After creating document type RE, execute VA02 transaction, select line item, select delete line item icon.  The system goes into runtime and just stays there.  No error message, no abap dump.  To escape the transaction, I have to select 'stop transaction'.
    I have tested all other document types we use in our system,  (including our customized transactions) SO, CR, DR, etc., and the system allows line item deletion.

  • Change the backend doc type from PR to PO in BADI BBP_TARGET_OBJECTS.

    Hi,
    We have followed below approach for backend document type determination.
    1. A custom function module contains the logic to determine the backend document type of a Shopping cart line item. THis function module, performs many checks and hence cannot be called in any BADI that is executed in Foreground.
    2. I am using BADI BBP_TARGET_OBJECTS to change the follow document type by calling the custom function module.
    Issue here is, if the backend document type of a line item is Purchase requisition (2) by SAP standard, and if I try to change it to Purchase order, it gives run time error and ends up in creation of Purchase order.
    After further investigation I found that this line item (with default backend doc type as 2) has a desired vendor. If we change the desired vendor of this line item to fixed(To Partner function 19 from partner function 39), it allows us to change the doc type from Purchase requisition to purcahse order in BADI BBP_TARGET_OBJECTS.
    But changing the partner function is possible only in BBP_DOC_CHANGE BADI, and I cannot call the custom function module there, as it may impact the performance.
    Is there any other way, I can change the partner function in any of the BADIs called in background?
    Or Is there any way by which I can change the backend document type from PR to PO in BBP_TARGET_OBJECTS?

    Hi Parab
    if you swaping 39 to 19 viadoc change badi
    REQUESTER has a control on Purchase ORDER Vendor and BUYER lost a control so your business has to decide.In this case procurement department lost their control.
    Fixed vendors are like inforecord and contract negotiated for best price ..
    Muthu

  • Sales doc type

    Hi,
    If in a business having Plant Sale,Depot Sale & Export slaes then I have to create one sales doc  type-ZOR1 for all types of sales & one document catgory & one pricing procedure.,Please give me the solution.
    Thanks,
    Siku.

    Hi,
    Can you be more clear with your question?
    But in case if you are asking whether you can use 1 doc type and 1 pricing procedure for different kind of sales scenario then answer to that is you can still use 1 doc type for plant/depot./export sales but its not advisable esp for depot sales u should use STO (stock transport order) for which already seperate doc type has been provided by SAP.
    Also when coming tp pricing procedure its advisable to have seperate pricing procedures only for domestic/export sales as well as depot sales as the CTs would be varying as in terms of freight, taxes, surcharges etc (as applicable and as per country laws) and you need to take into consideration the excise implications ( or depot sales)
    Regards,
    Kant

  • Assinment of pricing procedure to doc type

    Hi friends,
    I am new to MM , how the pricing procedure is assigned to doc type, or how the pp is triggered in PO.
    Thanks
    madhu

    Hi Madhu Sudan,
    Pricing Procedure as you know is one and the same as calculation schema.
    To administer the PP i.e. Determination of Calculation Schema for PO you will have to go to the transaction SPRO---SAP Reference IMG
    Follow the node
    Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Calculation Schema.
    Once you are there In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence
    Now coming to your query,
    1) Assignment a Calculation Schema (PP) to Doc type
    -- Remember It is not possible to assign PP to Doc type
    2) Trigerring of PP in PO
    -- Follow these underwritten simple steps:
    i.  Define a schema group for vendor under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. You will have to assign this same schema group in the relevant vendor master record.
    ii. Define a schema group for Purchasing organisation under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. & assign it to the relevant Purchasing Organisation in the same step.
    iii. Once this is done you have to Determine Calculation Schema for Standard Purchase Order under the node>Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema Determination. In this step you assign Calculation Schema to a combination of Schema Group (Purchasing Organisation) & Schema Group (Vendor).
    iv. Conclusion: During the time of making a PO; Shema Group of Vendor is picked from the relevant Vendor Master Record, Schema Group of Purchasing Organisation is picked from Customisation (where you assigned it) & A Calculation Schema is triggered for the combination of these two Schema Groups (PP that you defined in step iii)
    Hope this explains it, for better understanding please read the IMG activity documentation for each activity.
    For any further doubts please reply.
    Regards,
    Prithviraj

  • Default  Doc Type for PO

    Hi Friends..
    I need your help in solving a Puzzle in SAP.
    I want to use ME59N automatic po conversion option for creation of PO from PR.Here PR doc type is NB-Standard, I want PO doc type to be my own doc type " CT3 " doc type. I have made below settings,
    a.Activated Auto PO in VMR.
    b.Activated Auto PO in MMR
    c.Linked my CT3 doc type in SPRO.
    But, when I tried to do default doc type settings in SPRO, SAP didn't
    accept this Tcode (ME59N) & hence not successfull.
    SAP is taking default doc type as NB & not tailor made "CT3" doc type.
    Pl respond.
    Thanks,  VK.

    Hi,
    You hve done settings for Automatic PO, I think those setting are not required for you. Because your scenario is not Automatic PO.
    In ME21N transaction you can do personnel settings with this whenever you run the ME21N tcode by default system will pick tht doc type as default doc type. This can be user based setting.
    Hve you maintained the combination of PO document type and PR docuement type ? If you are using onli CT3 PO document type, assign this PO document type only.
    In SPRO - MM - Purchasing - Define default Doc types maintain the defulat doc type for ME21N transaction.
    Hope its clear, still if u hve questions let me know.
    reg
    Durga
    *Assign points if the info is useful

Maybe you are looking for