Using supplier invoice value in customer billing

Hi,
We have a third party sales scenario where we are required to charge the customer based on the vendor invoice that was issued. The vendor invoice could be lower / higher than the price in the Purchase order.
Is there a way to be able to update the pricing condition in the billing document based on the vendor invoice that was received ?
Would appreciate your valuable inputs.

Hi,
Use the form-routine "userexit_pricing_prepare_tkomp" of user exit "RV60AFZZ".  change communication structure XKOMV to update the pricing details.
Regards
Vinod

Similar Messages

  • Vendor invoice value in customer billing

    Hi,
    We have a third party sales scenario where we are required to charge the customer based on the vendor invoice that was issued. The vendor invoice could be lower / higher than the price in the Purchase order.
    Is there a way to be able to update the pricing condition in the billing document based on the vendor invoice that was received ?
    Would appreciate your valuable inputs.

    Hello,
    in third-party process, the Cost of billing document is determined from PO or invoiec recepit value. Please check the note 372772.
    Best regards,
    Ivano.

  • Negetive Invoice Value in Custom ODS

    Hi Friends,
    We are loading the delta data from 2LIS_13_VDITM ( Delta is ABR  ) to one custom Infocube & one custom ODS parllely.
    For some new invoices created in R/3 , ODS is showing negative invoice qty &value, but cube is showing correct positive invoice qty & value? ( these invoices are not the cancelled invoices )..
    What might be the reason for negetive value in ODS please?..
    thanks all for the inputs..
    Regards,
    Srikanth

    Hi Kanth,
    It sounds to me as if you are using a routine for the KF in eather the update rule/transformation to the cube or the DSO.
    The KF might be multiplied by -1 depending on if the posting is a debit or credit posting. The char. 0DEB_CRED should indicate this.
    Hope it helps.
    BR
    Stefan.

  • Discussion About The Use Of Project Server 2013 Timesheet Custom Billing Categories (Post SP1 and April 2014 CU Install)

    In support of a consulting company using timesheet custom billing categories to designate project time as billable onsite, billable offsite, and non-billable, I've encountered a series of issues which appear to be associated with the custom billing category
    timesheet lines.  These issues cause timesheet users to get frustrated, and contribute to misalignment between project actuals and timesheet actuals.  We're in Single Entry Mode, no pre-population, SP1 and April 2014 CU Installed.
    I'll enumerate the issues here and pose the question to the community as to whether others are experiencing any/all of these things, and if so,  ask if any workarounds have been discovered.  We're working with Microsoft to validate these independently,
    but I am posing the questions to the community to gather additional information, and hopefully save some folks time in troubleshooting similar issues.
    1.When time is entered on an assignment into timesheet lines of multiple billing categories, only time entered since the last save is getting saved and ultimately sent, on timesheet submit, to the approval center.  Although the previously entered and
    saved time appears in the application interface when the timesheet is re-opened, only data since last save is actually saving to the server or processing through the approval center.  We believe this is the primary cause for timesheet and project actuals
    being out of alignment.
    2."_ Error Loading".  When assignments are added, deleted, or changed after a timesheet has been created, standard timesheet lines are added, deleted or changed (i.e. synchronize) with the assignments. However, for custom billing category
    timesheet lines, they do not change when the assignments change, and they aren’t removed if the assignment is removed.  We believe this causes secondary errors, like the "_Error Loading"  (and others as will be described below).
    3.When a timesheet with time in a non-standard billing category is deleted and recreated, time is arbitrarily moved to standard timesheet lines for the same assignment. If the task assignment is subsequently removed, the timesheet line causes the timesheet
    to break.
    4."Error Communicating with Server". When trying to submit a timesheet, a pop-up box appears indicating that there is an error communicating with the server.  This error appears because a timesheet line is no longer associated with a project.
    In order to submit the timesheet the orphaned timesheet line must be identified and manually removed. One technique we found which helps to identify an orphaned timesheet line is to select a task and submit task progress. Repeat for all timesheet lines until
    you get an error.  The timesheet line(s) with the error can be manually removed from the timesheet, fixing the error.
    5. Unable to Open Specific Timesheets without Error. There are certain scenarios when the "Remove Task" feature is used or an assignment is otherwise removed after creation of a timesheet with custom billing category lines, which causes orphaned
    timesheet lines. These orphaned lines can cause issues when trying to open a timesheet. The issue can appear when timesheets are in progress in multiple periods. In the problematic scenario, time is entered and submitted in one period and subsequently
    the task is 'removed' from another period before the PM processes the first approval request. Process governance can certainly help here, but improvement in the way synchronization occurs between project assignments and custom billing category timesheet lines
    would be great. The error can often be resolved by re-adding the assignment for the problematic timesheet user to the project (which creates a new assignment), and then allows you to open the timesheet.  Then time can be moved from the old timesheet
    line to the new timesheet line, and the old one can be removed.
    In 4 and 5, sometimes we can't open a timesheet without error, and other times we can open it but not submit it. We are not 100% clear on all the different causes for each. Each of these issues are suspected to be contributing the the misalignment of
    data between project actuals and timesheets, which can be a real problem for external projects for which time collected through timesheets are being used to generate invoices.
    Although these may seem like separate issues, warranting separate questions, I decided to post them together because they all seem to be related to synchronization of project assignments and timesheet lines for custom billing categories.
    Any thoughts or suggestions from the community would be appreciated.
    Best regards,
    Justin
    Justin Naughton

    There are many causes for each of the errors mention.  It would be best to put one issue to the forum at a time.  For example, some of these issues occur then tasks are deleted from projects but a timesheet has been submitted.   Depending
    on the scenario, some of these issues have been fixed with the latest service pack.
    Other issues are due to bad scheduling habits with the project managers and so first determining what they have done can help resolve some the issues.
    _error Loading, is because something is NULL in the data and the jave is choking when it build the form. Again, these may be because of delete tasks, resources, projects  or someone doing copying and pasting of rows.
    cheers!
    PS.  Train your PM to not COPY and PASTE rows in project schedules.  It can be done, but it can create problems.  There are over 500 fields and some have unique data and the copy paste creates havic.
    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

  • BTS 2013 - How to Enable BizTalk to Use the Supplied ISA11 Value on a File Instead of the Value Set in the Agreement ("^", "U")

    I have a case where a trading partner sends two separate file types: a 999 acknowledgement (uses the carat separator) and a 277U (uses the "U"). The trading partner uses the same ISA6/ISA8 identifiers. The 999 acknowledgement
    cannot be defined in the Transaction Set List so I need to support all transaction sets in the agreement. For the 277U, I can set the 277 in the set list, but then having multiple agreements with the same ISA6/ISA8 is not allowed. The type
    of file we accept is directed to an orchestration via the receive port/receive folder (999 files go to one folder and 277U files go to another).
    I would like to be able to accept the file and let BizTalk determine the repetition separator by reading it from the supplied ISA11 value rather than the set value in the agreement. Is this possible?

    Here's the thing, all other HIPAA transactions define ISA11 as Repetition Separator so having an ISA11 value of 'U' on a 277U is an outlier. 
    Let me alter my advice...the first thing you should do is check their Companion Guide for the 277U to see if they have specified the interpretation of ISA11.
    But, looking at the 277CA Implementation Guide, ISA11 is defined as Repetition Separator.  I don't have have the official 277U IG but if you can get a copy, that will decide this definitively.
    So, I would raise it as a bug on their side.
    However, if they insist on remaining non-compliant, you then have to get them to document to you the exact meaning of ISA11 since they're causing some ambiguity.  If they are sending 'U' as Standards Identifier, they I would use a custom Pipeline Component
    to change 'U' to '^' in EDI.

  • Customer ledger receivables are showing less as per Invoice value.

    Hi
    we have checked randomly and found that in few cases Invoice amount which is reflecting in our customer ledger is basic value insted of " net selling value" ( basic price + Tax Price ). Due to which in my customer ledger receivables are showing less as per Invoice value.
    If any body not understand this problem, please send email id.  i will send you screen shot.
    my email id: [email protected]
    Attaching Scrren shot of customer ldeger for customer " Tristar
    Attaching mannually working file for your reference

    Hi
    Is this RP/RW report or standard report ledger ...you are referring , if it is CO-PA report then it will the problem in the forkula. If you double clik on that field you will get the formula ....
    VVr

  • Unable to make use of Service "Release Supplier Invoice"

    We have recently installed EHP-3. I have been trying to make use of the following service
    Under Repository Browser --> Package -- > OPS_SE_IVE_XI_PROXY
    Enterprise Services -- > Server Proxies ---> II_IVE_E_INVOICEREPRELRQ (Double Click)
    The Service Release Supplier Invoice with Service Interface name --> InvoiceERPReleaseRequest_In has status Active.
    Everthing seems to in place... But I don't see the Service under SOA Manager.
    Please advice, how to make use of the Service above....
    Thanks in Advnace!!
    Vikas

    I have configured the Logical Port and able to publish other Services... but not able to find this Service itslelf under wspublish too..
    This is the message comes under Dispaly Logs "No service(s) to be published with the given criteria.
    Message no. MSG_CL_ER022"..
    Thanks for your help
    Vikas

  • Unable to use Service - Release Supplier Invoice

    We have recently installed EHP-3. I have been trying to make use of the following service
    Under Repository Browser --> Package -- > OPS_SE_IVE_XI_PROXY
    Enterprise Services -- > Server Proxies ---> II_IVE_E_INVOICEREPRELRQ (Double Click)
    The Service Release Supplier Invoice with Service Interface name --> InvoiceERPReleaseRequest_In has status Active.
    Everthing seems to in place... But I don't see the Service under SOA Manager.
    Please advice, how to make use of the Service above....
    Thanks in Advnace!!
    Vikas

    Vikas,
    To analyse your issue below, I would appreciate that you open an OSS ticket under component CA-SOA-WS with a detailed issue description (screenshots are very welcome).
    Thanks,
    Claudius

  • Blocking the change of Supplier Invoice Number on update using SP

    Hi Mentors,
    Just wondering if blocking the change of Supplier Invoice No. (OPCH.NumAtCard) is possible using SP_TransactionNotification?
    I've been trying to make it work with the following code:
    --Prevent Duplicate Supplier Ref. No. in AP Invoice
    if @object_type = '18' and (@transaction_type in ('A' ,'U'))
    begin
    declare @RefNo as varchar (100)
    declare @CardCode as varchar (100)
         if (@object_type = '18')
              begin
                 select @RefNo = NumAtCard, @CardCode = CardCode from OPCH T0 where docentry = @list_of_cols_Val_tab_del
                 begin
                   if (@RefNo is not null)
                     begin
                       if 1!= (select count (docentry) from OPCH  where (NumatCard = @RefNo) and (cardcode = @CardCode))
                         begin
                            select @error = 10
                            select @error_message = 'Duplicate Supplier Reference Number!'
                         End
                       End
                   End
              End
    End
    --Prevent Supplier Ref. No. in AP Invoice from being changed during update mode.
    if @object_type = '18' and (@transaction_type = 'U')
    begin
    declare @DocEntry as int
         if (@object_type = '18')
              begin
                 select @RefNo = NumAtCard, @CardCode = CardCode , @DocEntry = DocEntry from OPCH T0 where DocEntry = @list_of_cols_Val_tab_del
                 begin  
                       if (@RefNo != (select NumAtCard from OPCH where (CardCode = @CardCode) and (DocEntry = @DocEntry)))
                         begin
                            select @error = 10
                            select @error_message = 'Changing of Supplier Reference Number is not allowed!'
                         End
                       End
              End
    End
    I'm not sure if this is really possible,and that I could be just beating the wind by trying.
    Thanks in advance!
    Sean

    To avoid modifiing the vandor reference use this:
    IF @Object_type = N'18' and @transaction_type = N'U'
    BEGIN     ---
    declare @li int
    declare @pref nvarchar(100)
    set @li=
    (select max(t.LogInstanc)   from ADOC t
       where t.ObjType=18 and t.DocEntry=@list_of_cols_val_tab_del)
    set @pref=
    (select isnull(t.NumAtCard,'')    from ADOC t
        where t.ObjType=18 and t.DocEntry=@list_of_cols_val_tab_del
          and t.LogInstanc=@li-1)
    If @pref !='' and @pref !=
    (select isnull(t.NumAtCard,'')   from OPCH t
       where t.DocEntry=@list_of_cols_val_tab_del)
    Select @error = 10, @error_message = N'Changing of Supplier Reference Number is not allowed!'
    END     
    --- To avoid using duplicated reference try this:
    if @object_type = '18' and @transaction_type in (N'A', N'U') -- AP invoice
    BEGIN          ----
    declare @Invoice AS VARCHAR(15)
    declare @Card AS VarChar (20)
    SELECT @invoice = NumatCard, @card = CardCode FROM dbo.OPCH
         WHERE DocEntry = @list_of_cols_val_tab_del
    If exists (SELECT T0.cardcode, T0.NumatCard FROM OPCH T0 where T0.NumatCard = @invoice
               and T0.CardCode=@card and T0.DocEntry!=@list_of_cols_val_tab_del)
    Select error = 10, @error_message = N'Duplicate Supplier Reference Number!'
    END          ----

  • Using environment-supplied (GWEVENTS_MAXCOUNT) value of 256

    Hello,
    This morning we started having HIGH CPU utilization and TCP/IP connectivity issues with one of our POs. So I restarted the server, it is running fine but the PO screen has an error(event) in black "Using an environment-supplied (GWEVENTS_MAXCOUNT) value of 256"
    How can I fix that??
    We are at GroupWise 802 hp2, running on Netware 6.5 sp7. We also have BES 4.1 - Novell Data Sync 1.2
    Thank you, if you want I can email a pic of the error
    Ramiro
    [email protected]

    hme0,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://forums.novell.com/

  • Seeburger help required for Supplier Invoice (EDI 810) and Dispatch Advice

    Hi All,
    Pls let me blog/steps for scenario for Supplier Invoice and Dispatch Advice using Seeburger.
    For Supplier Invoice I assume R/3 will send data to Vendor (810).
    1. Pls let me know for R/3 to XI will we use INVOCE IDOC?
    2. Pls let me know for R/3 to XI Communication do we will use same Distributiion Model setup?
    3. Pls let me know what Seeburger BIC modules I need to use in Seeburger AS2/File Receiver Adapter
    4. Which Interface and Adapter  I need to use for 810 and which Interface and Adapter  I need to use for 997.
        Pls send its setup with its Mappings defined in Modules.
    5. What is Disptach Advice?  Is it also same like Supplier Invoice ? Does it also have EDI Number and if yes then what?
    Pls send me blogs for the above Supplier Invoice and Dispatch Advice settings.
    Regards

    >
    Rickkk wrote:
    > Hi Ravi and All
    >
    > I am thankful to all of you for great help of yours.
    >
    > Steps:
    >
    > 1) I wil create an INvoice in your backend system. It will generate an IDOC.
    > 2) This IDOC will be sent to my XI system.
    > 3) I will map the IDOC to the Target XML 810 --- From where I will get this Target XML 810 ?
    YOu have to login to the Physical box in which XI is installed (Take Basis Help.
    In one of the drives, you will find a folder called seeburger.
    Inside that folder, you can browse to find the XSD structure for your 810 .
    YOu will find different XSDs for different versions of 810.
    Suppose your EDI 810 version is 4010, then you have to use the XSD for 810 4010 version (There will be separate folders for each transaction set/version combination.
    It will be there also in the software CD that seeburger provides when you buy it.
    > 4) I need a seeburger receiver AS2 adapter that consist of modules that will convert the XML 810 docuemnt to EDI document.
    >
    > Below are the modules will be present in you suggested seeburger receiver AS2 adapter
    > module key                  Parameter name               Parameter value
    > bic                                destSourceMsg               MainDocument
    > bic                                destTargetMsg                MainDocument
    > bic                                mappingName                  <the name of your X2E mapping for 810>
    > exit                               JNDIName                         deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
    >
    Yes.
    > 5. As per blog  -
    /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    >
    > For 997 Interface we are using seeburger Sender adapter and for 850 Interface we are using Split997 Sender adapter -- Reverse order
    >
    > For this scenario will it be like this again like
    > For 997 Interface we will use Seeburger Receiver AS2 Adapter where the above modules are configured -- Pls suggest
    >
    > For 810  Interface we will use Split997 Receiver adapter -- No modules configured Pls suggest
    >
    > I request you to kindly send me snapshots or blogs which has snapsot for this scenario.
    >
    No need of split 997 in outbound case. In this case, you will send the 810 and the partner will send the 997.
    So, to receive that 997 file, you need another scenario. You need the split 997 communication channel only in inbound case like in 850, but not in outbound case.
    > Last point -- is Dispatch advice direction is like 850 (Inbound ) or its direction is like 810 (outbound)?
    > Do we have IDOC or something like that present and its mapping ?
    >
    like I said earlier, it is an outbound document if your company is the vendor.
    It will be inbound if your company is the Customer to some other company.
    The IDOC that is used usually will be DESADV idoc.
    > Regards

  • Condition type used for invoice list

    Hello Gurus,
            following condition type used for invoice list, why do they exit in invoice list:
             RL00    MW15.  LR00    RD01

    Hi,
    Please go through the below document
    When you work with invoice lists, you need to be familiar with the following concepts:
    Prerequisites for invoice lists
    Relationship to Pricing
    Structure of an Invoice List
    Changing header and item data
    Integration with financial accounting (FI)
    Prerequisites
    You can only process invoice lists if the following prerequisite data is defined by your system administrator in Customizing for Sales:
    Condition type RL00 (factoring discount) must be maintained and, if required, also the condition type MW15.
    An invoice list type must be assigned to each billing type that you want to process in invoice lists. The standard version of the SAP R/3 System includes two types of invoice lists: LR for invoices and debit memos, LG for credit memos.
    Copying requirements must be defined (for example, the payer, terms of payment and other fields that must be identical in the documents to be included in the invoice list)
    In addition, before you process an invoice list, you must maintain the following master data:
    A customer calendar must be defined, specifying the time intervals or dates on which invoice lists are to be processed.
    The customer calendar must be entered in the Billing Sales Area view of the customer master record.
    Pricing condition records for the condition type RL00 and, if necessary, (e.g. in Germany) the condition type MW15 must be maintained.
    Output condition records for condition types LR00 and RD01 must be created.
    Relationship to Pricing
    The system processes factoring discounts in invoice lists in exactly the same way as other kinds of pricing elements. The data for the factoring discount is stored in condition records. Controlling during document processing is carried out via condition types, pricing procedures and access sequences. This control data is defined in Customizing for Sales by your system administrator.
    For further information, see  Conditions and Pricing.
    Structure of an Invoice List
    An invoice list represents an individual billing document. It consists of a document header and document items. Each item represents a billing document that you have included in the invoice list. The header contains an overview of summary information, such as the net value of all documents in the invoice list, the value of the factoring discount, details of taxes, and so on. It also contains information on partners and output.
    Changing Header and Item Data
    You can change some of the header data - for example, the billing date - when you process the invoice list. You can change an item - either an individual or collective invoice - and display document details. However, you cannot change any data in individual billing documents once they are part of an invoice list.
    It is possible, however, to make certain global changes to output in all items in an invoice list.
    For further information on output, see  Communication in Sales and Distribution Processing.
    Integration With Financial Accounting (FI)
    The documents that you want to combine within an invoice list must already have been billed and forwarded to Financial Accounting. Here the billing documents intended for an invoice list are blocked for normal dunning transactions.
    The dunning block on FI documents is lifted as soon as you create an invoice list and transfer it to FI . The system then calculates the new dunning date for the invoice on the basis of the invoice list date.
    In addition, the system enters invoice list numbers in the FI documents as reference numbers. Invoice list numbers can then be entered for incoming payments.
    When you save the invoice list, the system automatically creates an accounting document for the factoring discount and possible taxes and posts it to the corresponding G/L account in FI.
    Regards,
    Murthy

  • Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help the client in Data Mapping activity.

    Hello All,
    Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help in Data Mapping activity.
    Thanks,
    Mownesh

    There are standard templates in HCI data sources.
    e.g. 1) Customer Master data template is SOP_MD_CustomerMaster for extracting master data from SAP ECC and load it to S&OP
    KNVP is the table for customer in ECC from that you can select the fields as required
    KUNNR for customer Number
    ADRNR for Address
    List of a few commonly used table names of ECC:
    Product Related:
    MARA – Material Master (MATNR)
    MARC – Material Master with Plant Data (MATNR, WERKS)
    MARD – Material Master with Storage Location Data (MATNR, LGORT, WERKS)
    MAKT – Material Master Material Descriptions (MATNR, MATKL)
    MBEW – Material Valuation Data (MATNR, BWTAR)
    MVKE – Material Master : Sales related Data
    MDKP, MDTB – MRP related Data( Header, Item)
    MCHA, MCHB – Material Batches (Header, Item) (MATNR, WERKS, LGORT, CHARG)
    Vendor/Supplier related:
    LFA1 – vendor data (LIFNR)
    LFB1 --  Company Code Segment : Vendor Data(LIFNR, BUKRS)
    LFC1 --  FI Related Vendor Data (LIFNR, BELNR)
    LFM1 – Pur. Orgn. Related Vendor Data (LIFNR, EKORG)
    PReq/PO, BOM Related:
    EBAN – Pur. Req. Data( BANFN, BNFPO, BADAT, MATNR)
    EINA – Purchase Info. Record(General Data)(INFNR, MATNR, LIFNR)
    EINE – Purchase Info. Record (pur. Orgn. Data) (INFNR, EKORG)
    ELBK, ELBN, ELBP – Vendor Evaluation Related Data
    EKKO – PO Data (Header) (EBELN, BSTYP, BSART)
    EKPO – PO Data (Item) (EBELN, EBELP, MATNR)
    Pur. Req., RFQ and PO are differentiated by Doc Type (BSTYP) in EKKO table.
    For RFQ it is ‘A’ and for PO it is ‘F’
    MKPF – GRN Data (Header) (EBELN, BLDAT, BUDAT, XBLNR, BKTXT)
    MSEG – GRN Data(Item) MBLNR, BWART, LIFNR, MATNR, EBELN)
    Apart from this there are lot of tables which begin with ‘M’ & ‘E’, but we
    use the following very often.
    EQUK – Quota (Header)(QUNUM, MATNR)
    EQUP – Quota (Item) (QUNUM, QUPOS, LIFNR)
    EKBE – PO History Data (EBELN, EBELP, BELNR, BLDAT, MATNR, VGABE)
    EKBZ – PO History with Delivery Costs(EBELN, BELNR, LIFNR, XBLNR)
    EKET – Schedule lines data of a PO(EBELN, EINDT, SLFDT)
    EKES – Vendor Confirmations Data (EBELN, EBTYP, EINDT, XBLNR)
    T163F – Confirmation Texts (EBTYP, EBTXT)
    T156 – Movement Types (BWARE)
    T024 – Purchasing Groups
    T024E – Purchase Organizations
    T163 – Item Category’s in Purchasing Documents(PSTYP)
    T149D – Valuation Types
    T134 – Material Types
    FVLK – Delivery Types
    STKO, STPO – BOM(Bill Of Material) related Data (Header & Item)
    STPU, STPN, STST, STZU – BOM Related Tables
    RKPF, RBKP, RSEG (Header & Item) – MM – FI Related Data
    KONO, KONH – Pricing data
    T006 – Basic Unit Of Measurements
    Customer/Sales Order Related:
    VBAK : Sales Document(Header Data) (VBELN)
    VBAP : Sales Document(Item Data) (VBELN, POSNR, MATNR, ARKTX, CHARG)
    Enquiry, Quotation, Sales Order are differentiated based on Doc.
    Type(VBTYP Field) in VBAK, VBAP Tables for Enquiry VBTYP = A, for Quotation ‘B’ & for Order it is ‘C’.)
    LIKP : Delivery Table(Header Data) (VBELN, LFART, KUNNR, WADAT, INCOL)
    LIPS : Delivery Table(Item Data)(VBELN, POSNR, WERKS, LGORT, MATNR, VGBEL)
    (LIPS – VBGELN = VBAK- VBELN, LIPS-VGPOS = VBAP-POSNR)
    VTTK : Shipment Table(Header Data) (TKNUM)
    VTTP : Shipment Table (Item Data)(TKNUM, TPNUM, VBELN)
    (VTTP – VBELN = LIKP – VBELN)
    VBRK : Billing Table(Header Data) (VBELN, FKART, BELNF)
    VBRP : Billing Table(Item Data) (VBELN, POSNR, FKIMG, NEWR, VGBEL, VGPOS)
    (VERP – AUBEL = VBAK- VBELN, VBRP – VBEL = LIKP – VBELN)
    Apart from these tables there are lot of other tables which starts with ‘V’, but we use the
    following tables frequently.
    VBUK: All Sales Documents status & Admn. Data(Header) (VBELN, VBTYP)
    VBTYP = ‘C’ (Sales Order) VBTYP = ‘L’(Delivery) VBTYP = ‘M’(Invoice)
    VBUP: Sales Documents status & Admin. Data(Item) (VBELN, POSNR)
    VBEP : Sales Document Schedule Lines Data (VBELN, POSNR, EDATU, WMENG)
    VBKD: To get sales related Business data like Payment terms etc.(VBELN, ZTERM)
    VBFA: Sales Document flow data(VBELV, VBELN, POSNV, VBTYP)
    VBPA: Partner functions Data(VBELN, PARVW, KUNNR, LIFNR)
    TVLKT: Delivery Type: Texts(LFART, VTEXT)
    KNA1, KNB1, KNC1 : Customer Master Data and Other Partner’s Data(KUNNR,
    NAME1,LAND1)
    KNVK: Customer Master Contact Person(PARNR, KUNNR)
    KNVV: Customer Master Sales Data.
    LFA1, LFB1, LFC1: Vendor Master Data(To get Transporter data)(LIFNR, NAME1, ORT01)
    MARA, MARC, MARD : Material Master Data(Basic, Plant, St. Location Views)
    TVKO: Sales Organizations(VKORG)
    TVKOV: Distribution Channels(VTWEG)
    TVTA: Divisions(SPART)
    TVKBZ: Sales Office(VKBUR)
    TVBVK: Sales Group(VKGRP)
    T077D: Customer Account Group(KTOKD)
    T001W: Plants(WERKS)
    T001L: Storage Locations(LGORT)
    TWLAD: To get address of Storage Location and Plant(LGORT, ADRNR)
    TVAU: Sales Document (Order) Types
    KONV: Condition Types (pricing) (KNUMV, KSCHL, KWETR)
    T685T: Condition Types Texts.
    ADRC: To get Addresses of Partners
    VBBE, VBBS: Sales Requirements Data
    VBKA: Sales Activities Data
    VBPV: Sales Document Product Proposal
    Based on the functionality you can search ECC table names and fields
    Hope this information is helpful for you.
    Thanks and Regards,
    Anjali

  • V IMP : Report for Cash Customer Bill wise details

    Hi ABAP Gurus,
    Any body is having the report on Cash Customer Bill wise Details (with invoice details) ? Input criteria - Company Code, Plant, Cash Customer Name(customer Name given while creating cash customer) & Date Range(Document date). I am using the tables BSEC,BKPF,VBRP,BSAD,BSID. Out put i have to get Date, Doc No, Particulars QTY UOM Material Rate and Gross amount(Opening & Pending Amount) as line items.
    Please send me code on this. It's very urgent. Tomorrow is it's delivery date.
    I will reward points.
    My mail ID is [email protected]
    Thanks and Regards,
    Sundeep.

    Hi,
    Check the following links:
    http://www.sap-img.com/sap-fi.htm
    http://www.sapbrainsonline.com/TUTORIALS/FUNCTIONAL/FI_tutorial.html
    Regards,
    Bhaskar

  • Error in the execution of custom billing extension in PA module

    Hi All ,
    We had a requiremnet for creating the custom billing extension similar to the standard Revenue calculation billing extension . The change required in the formula for calculating the revenue was the Actual total burdened cost will be the Actual total burdened hours and Budgeted baselined burdened cost will be the Budgeted baselined burdened hours .Rest of the entity in the standard revenue calculation program will be as per the standard revenue billing extension.
    The standard formula is as follows :
    (1)     revenue amount = Lesser of (Remaining Funding Available if hard limit used) and ((AC / BC (BR – ER) – AR)
    I created a package which will get the value of AC and BC as per the client requirement . Defined the Extension using PROJECT BILLING SUPERUSER >> SETUP>> Billing >> Extension screen .
    This extension was then assigned to a project type . WE created a project using the same project type . When we fire PRC: Generate Draft Revenue for single project and pass the project number it first calls the Standard billing extension and then the custom one becoz of this there is error in calculating the revenue through it .
    We are not sure where we are going wrong . The standard extension has been end dated too ..still everytime it executes the standard and then the custom one .
    Has one faced such issue ? Request for some pointers to solve the issue.
    Thanks and Regards
    MN

    Hi,
    My issue got solved. It was beacause there was a method in a Bean Interface which did not have an implementation in the Bean EJB.
    appc just gave a NPE.
    The issue came out when i did a weblogic.ejbc.
    Thanks.

Maybe you are looking for