Sales data flow

Hello Experts,
This is my first post in this forum. Kindly help.
In my sales data flow, I have header and item data for deliveries, orders and billing. What should be my best data flow if I am trying to build a EDW?
a. Orders, Deliveries and Billing, say each have two DSO's, one for header and one for item. That means for the three areas, 6 DSOs. Consider Orders only now. Should I load the order header and order item into two seperate cubes and then join them by a multiprovider to get a multiprovider for Sales Order. And create similar cubes for deliveries and billing. And if I wanted to consolidate all three areas, then  could I have a multiprovider with 6 cubes (2 each for order, delivery and billing - header and item) ?
b. Or should I have a Consoliadtion DSO on top of Orders header and item so that I have a DSO with order information with header information stamped on each of the item records? and have similar consolidation DSO's for deliveries and billing? (that means extra data loads) and then load an order cube with data from the consolidation order DSO? and similarly two more cubes for biiling and dels? and then have a MP on top of these three cubes?
c. Or should I have just one cube with all order, delivery and billing information, loaded from three different consolidation DSOs?
For all of the above, how does delta changes impact the cube load? where should I use write optimzed DSOs?
Sorry for a long question, but I want to seletc the best design and would like your help
I will give points
Yanz Zemik

SD
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customer’s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents – the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge – creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
In Simple steps
The flow is something like this:
1. A sales order is created in R/3 by 'va01'.
2. A check on credit limit is carried out by the system (if configured)
3. In case credit limit is exceeded by creation of this order then the same needs to be subjected to approval.
4. On approval, order picking and delivery document is created wrt to the order document - this is equivalent to selecting ordered material from warehouse and stocking in the loading bay of the warehouse - inventory of inished goods reduces at this point of time.
5. Subsequently a billing document is created - this step realises the fact that revenue is generated.
6. There is a concept of open orders - basically anything in the order document that is partially serviced ( due to non-availability of stocks ) -
the delivery and billing
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
Also please check this links.
http://www.sapgenie.com/sapfunc/sd.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sapgenie.com/abap/tables_sd.htm
Check this link:
Basic Functions and Master Data in SD Processing
http://help.sap.com/saphelp_47x200/helpdata/en/90/758534c960a134e10000009b38f83b/frameset.htm
SD Tables
http://www.sapgenie.com/abap/tables_sd.htm
Please check this SD online PDFdocuments.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCSD/CAARCSD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_SD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSD/BCBMTWFMSD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOLISPLN/LOLISPLN.pdf
Also please check this SD links as well.
http://help.sap.com/saphelp_47x200/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sap-img.com/sap-sd.htm
http://www.sapgenie.com/abap/tables_sd.htm
http://searchsap.techtarget.com/featuredTopic/0,290042,sid21_gci961718,00.html
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html
All help ebooks are in PDF format here
http://www.easymarketplace.de/online-pdfs.php
Hope it helps

Similar Messages

  • How to obtain the pricing condition data from sales data?

    Hi all!  I have googled many times and read through many sites to understand how I can obtain the pricing condition data that's specific to a specific sales line.  However, the answer I got usually are as follow:
    Tables to be used:
    KONV
    KONH
    KONP
    VBRK
    VBRP
    And the thing is to obtain KNUMH data from VBRP and link it to KONP which will get the exact pricing condition data that's relating to the specific transaction.
    However, my challenge is that the field KNUMH in either VBRP or VBAP, it is empty.  Therefore, how can I have a report with my sales data as the primary file, and appending the pricing condition data so that I can analyze the different kinds of pricing condition types that the company is using.  The only field that I can use is KNUMV which does not give me the pricing condition that was used in this particular invoice line.
    I also know that there is the A*** tables, which contains the KNUMH file.  However, this file is split into many different tables.  Thus, is there a more efficient method to download all the data?  In any case, I still do not know how to link to my sales data.
    FYI, I only have SE16N and VK13's access.
    I hope that someone can help me, please!
    Thank you!

    Hi,
    Data flow :
    BW :
    When u right click on the Master Data Info object -> Select Data flow.Then  it will  show u the details like DS name,IS (If 3.x)
    Once u know the DS then you need to find out the source tables for the R/3 DS.This information will get using ROOSOURCE or ROOSFIELD tables  or help.sap.com.
    My suggestion better to search in Help site for DS source tables.
    DS Tables :
    The following link will provide you the source tables for some of the LO DS.
    https://wiki.sdn.sap.com/wiki/display/BI/BWSDMMFIDATASOURCES
    Regards
    Ram.
    Edited by: Ramakanth Deepak Gandepalli on Dec 22, 2009 9:29 AM

  • Data flow in R/3 and CRM

    Hi experts
    I am bit confused about the data flow in source systems moving to Delta queue even though i know bits and pices but not able to relate and keep them in order.
    First Scenario- R/3
    When we save a transaction or create a sales order by V1 it will go to Database tables and then through V1 it will reach the Extraction queue or Update tables based on the delta method we select or else if direct delta it will go directly to the Delta queue which is nothing but QRFCOUT AND ARFCQUEUE tables.
    in SM53 we can check the transfer of data records from this delta queue to BW.
    Is my understanding right on the R/3.
    Second scenario- CRM
    when we save a transaction lets take an example of Activity creation how does this pass to Delta queue and to the Database tables and is their a intermidate place where we can check the data in between the Transaction creation and till the Delta Queue of CRM.
    thanks and regards
    Neel

    Hi Rahul,
    Execute Transaction: CRMC_R3_ORG_GENERATE
    Select the org u want to copy to CRM.
    Click on 'Generate Selected Lines'.
    Best Regards,
    Pratik Patel
    <b>Reward with Points!</b>

  • AR DATA FLOW (TABLE LEVEL) - INVOICE편

    제품 : FIN_AR
    작성날짜 : 2003-09-16
    AR DATA FLOW (TABLE LEVEL) - INVOICE편
    =====================================
    PURPOSE
    이 문서에서는 AR table들에 대해 어떻게 data가 들어가는지에 대해
    설명한다.
    Invoice transaction을 기준으로 설명한다.
    Explanation
    1. Invoice
    User가 invoice를 입력하면, 아래의 table들에 data가 insert된다.
    o RA_CUSTOMER_TRX_ALL (Invoice Header)
    o RA_CUSTOMER_TRX_LINES_ALL (Line Details)
    o RA_CUST_TRX_LINE_GL_DIST_ALL (Information for posting to GL)
    o RA_CUST_TRX_LINES_SALESREPS_ALL (Sales Credit Information)
    일단, invoice가 "Complete"되면, 아래의 table에 한줄(혹은 그 이상)이
    추가로 Insert된다.
    o AR_PAYMENT_SCHEDULES_ALL (Running Totals for Invoice Amounts)
    대체로 하나의 invoice는 하나의 Payment schedule record를 가지지만,
    만약 할부(Installment)로 Pay처리되는 invoice라면, installment하나당
    하나의 Payment schedule record를 가진다.
    | | /| |
    | TRX |---------------<-| PAYMENT |
    | | \| SCHEDULE |
    | |
    | |
    ^ -------
    /|\ |
    ------------ |
    | | |
    | TRX_LINES | |
    _| | |
    / ------------ |
    | | | |
    \__/ | |
    ^ |
    /|\ |
    | |
    | GL_DIST |
    | |
    1.1 RA_CUSTOMER_TRX_ALL
    Invoice의 Header정보(Customer, Invoice Number, date.. etc)를 담고 있는 table이다.
    Invoice하나당 한줄의 정보가 Insert된다.
    Key = CUSTOMER_TRX_ID (generated from sequence RA_CUSTOMER_TRX_S)
    Important Fields
    TRX_NUMBER - User Entered Invoice Number
    CUST_TRX_TYPE_ID - Foreign key to RA_CUST_TRX_TYPES
    BILL_TO_CUSTOMER_ID - Foreign Key to RA_CUSTOMERS
    SHIP_TO_CUSTOMER_ID - Foreign key to RA_CUSTOMERS
    TRX_DATE - Invoice Date
    COMPLETE_FLAG - Y or N
    1.2 RA_CUSTOMER_TRX_LINES_ALL
    Invoice의 Line정보(수금 item및 금액, Tax등)가 insert되는 table이다.
    Invoice하나당 한줄이상을 가진다.
    Key = RA_CUSTOMER_TRX_LINE_ID (from sequence RA_CUSTOMER_TRX_LINES_S)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    LINE_TYPE - LINE, TAX, FREIGHT
    QUANTITY_INVOICED - Line Quantity
    UNIT_SELLING_PRICE - Price per unit
    EXTENDED_AMOUNT - Quantity * Price
    LINK_TO_CUST_TRX_LINE_ID - Null for LINE, for TAX and FREIGHT lines
    contains the RA_CUSTOMER_TRX_LINE_ID of
    associated LINE record
    1.3 RA_CUST_TRX_LINE_GL_DIST_ALL
    GL로 Posting될 정보가 담겨져 있다.
    Invoice Line당 한줄 + Invoice Header 한줄로 이루어져 있다.
    (예를들어, Invoice의 Line이 총 3줄이라면, RA_CUST_TRX_LINE_GL_DIST_ALL table에는 총 4줄의 정보가 담기게 된다.)
    Key = CUST_TRX_LINE_GL_DIST_ID (from sequence)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    CUSTOMER_TRX_LINE_ID - Foreign key to RA_CUSTOMER_TRX_LINES or
    Null if this relates to Invoice Header.
    AMOUNT - Value of distribution - entered currency
    ACCOUNTED_AMOUNT - Value of distribution - book currency
    CODE_COMBINATION_ID - Foreign key to GL_CODE_COMBINATIONS
    POSTING_CONTROL_ID - -3 if unposted
    GL_DATE - Accounting date.
    GL_POSTED_DATE - Date Invoice posted to GL.
    1.4 RA_CUST_TRX_LINE_SALESREPS_ALL
    해당 invoice가 입력될때 함께 입력된 Sales Person에 대한 정보가
    담겨져 있다.
    1.5 AR_PAYMENT_SCHEDULES_ALL
    해당 invoice에 대해서 Line, Tax, 운송비 등 각각의 항목에 대한 Total값과
    Remaining값을 담고 있다.
    대체로 Invoice당 한줄이 insert된다.
    Key = PAYMENT_SCHEDULE_ID (from sequence AR_PAYMENT_SCHEDULES_S)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    STATUS - (OP)en or (CL)losed
    ACTUAL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise
    date payment schedule closed.
    GL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise the
    gl date of the closing transaction.
    AMOUNT_DUE_ORIGINAL - Invoice Total Amount
    AMOUNT_DUE_REMAINING - Total Amount outstanding for Invoice.
    AMOUNT_LINE_ITEMS_ORIGINAL - Sum of Invoice Line amounts.
    AMOUNT_LINE_ITEMS_REMAINING - Outstanding Line amounts.
    TAX_ORIGINAL - Total Tax for Invoice.
    TAX_REMAINING - Outstanding Tax for Invoice
    FREIGHT_ORIGINAL - Total Freight For Invoice
    FREIGHT_REMAINING - Outstanding Freight
    AMOUNT_APPLIED - Total payments applied to this Invoice.
    AMOUNT_CREDITED - Total Credit Memos applied.
    AMOUNT_ADJUSTED - Total value of adjustments.
    The payment schedule should balance within itself, ie the following
    calculations
    should be true:-
    AMOUNT_DUE_ORIGINAL = AMOUNT_LINE_ITEMS_ORIGINAL
    + TAX_ORIGINAL
    + FREIGHT_ORIGINAL
    AMOUNT_DUE_REMAINING = AMOUNT_LINE_ITEMS_REMAINING
    + TAX_REMAINING
    + FREIGHT_REMAINING
    AMOUNT_DUE_ORIGINAL = AMOUNT_DUE_REMAINING
    + AMOUNT_APPLIED
    - AMOUNT_CREDITED
    + AMOUNT_ADJUSTED
    Reference Documents
    Note : 29277.1

    Hello,
    The basic flow of data is
    ERP tables - source snapshots - source views (eg MRP_AP%) - staging tables (MSC_ST%) - ODS tables ( MSC%)
    Check out note 412375.1. This is the flow for sales order data for ASCP.
    regards
    Geert

  • Data flows and technical terms

    Hi all,
    Anyone please give me SD data flow i.e what is sales order and when it will be generated and how it is linked with billing and delivery and what is invoice, cost centre, profit center, business area, wbs element etc.
    And also the purchase data flow ie Purchase order purchase requisition, material document etc.
    Provide me what exactly these mean in simple words.
    I am new to BI and i am very confused with these technical  terms.
    Regards,
    Nishuv.

    Hi,
    Cost centre & profit Centre Hierarchy:
    you have to look at the Implementation Guide (IMG) for Profit Center Accounting, Master Data -> Create/Change/Display Hierarchy or something similar..with Transaction Code:KCH3 .
    But if you want specfic one , need to build a specific hierarchy in R3 and load it in BW.
    You can also build it directly in BW.
    If it is product hierachy u have to generate the levels in R/3 side (using same transaction in SBIW), which activates PRODH1, PRODH2...etc.
    SBIW or SAP reference IMG under General Logistics -> Master Material -> Material or Settings for Central Fields -> Sales-Relevant Data -> Define Product Hierarchies
    Please check this link for the detailed procedure to create hiearchy;
    http://help.sap.com/saphelp_nw04/helpdata/en/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm.
    Create Hierarchy in R/3 -Sample
    http://www.bwexpertonline.com/go/sample/
    Pls chk this links;
    Re: Hierarchy Loading from R/3 to BW
    Product Hirarchies for 0MATERIAL (from R3)
    R/3 Hierarchy Text upload issue
    http://help.sap.com/saphelp_nw70/helpdata/en/b3/41cc373de44040e10000009b38f8cf/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/c6/f3dc3709e9ea12e10000009b38f8cf/frameset.htm
    Hope this helps,
    Regards
    CSM Reddy

  • F4 help and data flow

    Hi,
                 I created online sale order interactive form using ABAP. In web dynpro component I maintained Display type as native. In the form Layout type as ZCI layout. In form layout I drag and drop the Value help button and Submit button form web dynpro native tab. Now buttons are working but data flow is not happening so I am not able to create sales order.
                But if I use Display type as ActiveX ,form Layout as Standard, Buttons From Webdynpro activeX. In this case f4 help is not working but data flow was happening so I am able create sales order. I need f4 help and as well as I should able to create sales order.
    So please help me.
    Thanks & Regards,
    Krishna,

    Hi Mohan,
    For ZCI Layout in the Designer have you inserted the WebDynpro Script. If not goto Layout Designer and in the WebDynpro Tool Bar goto Utilities->(select) Insert WebDynpro Script.
    To check whether the Script is inserted or not, goto Palette->Heirarchy of Adobe Form Toolbar and in Heirarchy scroll down to Variables, in the variables you'll find one script object i.e. "containerFoundation_JS". If this is present then it will work.
    If it is not inserted then use the Report FP_ZCI_UPDATE.
    Regards
    Pradeep Goli

  • Extended Rebate Processing - Data flow in tables

    Hi Gurus,
    Can somebody help me understand how data flows through various tables in extended rebate processing. i.e. once a new condition record for a rebate agreement is created, in which table it is updated first? Once VBOF is executed, which are the tables taken as reference and which are the ones updated on execution.
    Please explain wrt all concerned tables and info-structures like KONA,KONV,KONH,KONP,S136 & S469.
    It'll be a great help if somebody could explain thoroughly.
    Thanks & Regards.

    Thanks Arun.
    I understand now that to have the extended rebate functionality we have to activate the generic Business Function- EA-ISSE (Industry specific sales enhancement).
    I am more interested in the Indirect sales functionality for which I understand we have to use the Pendulum List Indirect Sales component.
    I have a situation where I am a producer and I have wholesalers who have end customers. The end customers may or may not belong to a corporation(an umberalla organization) .
    I want to set rebates on the sales of the end customers. The sales details of the end customer would be given to me (producer) by the wholesaler. But the rebate payments, I (the producer) want to pay it out to the Wholesaler ( I understand the standard solution is to pay out to the end customer) with details of each end user rebates.
    Do you have any pointers to how this could be acheived?

  • COMM_SRTUCTURE is uknown when migrating data flow bw 3.x to 7.4

    Dear ALL,
    2LIS_13_VDHDR data flow migrating 3.x to 7.x , ABAP syntax error COMM_STRUCTURE is unknown infosoure transformation level, present we are using 7.4 sp5 . after migration ABAP code
    TYPES:
          BEGIN OF _ty_s_TG_1_full,
    *      InfoObject: 0CHNGID Change Run ID.
            CHNGID           TYPE /BI0/OICHNGID,
    *      InfoObject: 0RECORDTP Record type.
            RECORDTP           TYPE /BI0/OIRECORDTP,
    *      InfoObject: 0REQUID Request ID.
            REQUID           TYPE /BI0/OIREQUID,
    *      InfoObject: 0CALDAY Calendar Day.
            CALDAY           TYPE /BI0/OICALDAY,
    *      InfoObject: 0CALMONTH Calendar Year/Month.
            CALMONTH           TYPE /BI0/OICALMONTH,
    *      InfoObject: 0CALWEEK Calendar year / week.
            CALWEEK           TYPE /BI0/OICALWEEK,
    *      InfoObject: 0FISCPER Fiscal year / period.
            FISCPER           TYPE /BI0/OIFISCPER,
    *      InfoObject: 0FISCVARNT Fiscal year variant.
            FISCVARNT           TYPE /BI0/OIFISCVARNT,
    *      InfoObject: 0BILLTOPRTY Bill-to party.
            BILLTOPRTY           TYPE /BI0/OIBILLTOPRTY,
    *      InfoObject: 0COMP_CODE Company code.
            COMP_CODE           TYPE /BI0/OICOMP_CODE,
    *      InfoObject: 0DISTR_CHAN Distribution Channel.
            DISTR_CHAN           TYPE /BI0/OIDISTR_CHAN,
    *      InfoObject: 0DOC_CATEG Sales Document Category.
            DOC_CATEG           TYPE /BI0/OIDOC_CATEG,
    *      InfoObject: 0PLANT Plant.
            PLANT           TYPE /BI0/OIPLANT,
    *      InfoObject: 0SALESORG Sales Organization.
            SALESORG           TYPE /BI0/OISALESORG,
    *      InfoObject: 0SALES_GRP Sales group.
            SALES_GRP           TYPE /BI0/OISALES_GRP,
    *      InfoObject: 0SALES_OFF Sales Office.
            SALES_OFF           TYPE /BI0/OISALES_OFF,
    *      InfoObject: 0SHIP_TO Ship-To Party.
            SHIP_TO           TYPE /BI0/OISHIP_TO,
    *      InfoObject: 0SOLD_TO Sold-to party.
            SOLD_TO           TYPE /BI0/OISOLD_TO,
    *      InfoObject: 0VERSION Version.
            VERSION           TYPE /BI0/OIVERSION,
    *      InfoObject: 0VTYPE Value Type for Reporting.
            VTYPE           TYPE /BI0/OIVTYPE,
    *      InfoObject: 0DIVISION Division.
            DIVISION           TYPE /BI0/OIDIVISION,
    *      InfoObject: 0MATERIAL Material.
            MATERIAL           TYPE /BI0/OIMATERIAL,
    *      InfoObject: 0SHIP_POINT Shipping point.
            SHIP_POINT           TYPE /BI0/OISHIP_POINT,
    *      InfoObject: 0PAYER Payer.
            PAYER           TYPE /BI0/OIPAYER,
    *      InfoObject: 0DOC_CLASS Document category /Quotation/Order/Deliver
    *y/Invoice.
            DOC_CLASS           TYPE /BI0/OIDOC_CLASS,
    *      InfoObject: 0DEB_CRED Credit/debit posting (C/D).
            DEB_CRED           TYPE /BI0/OIDEB_CRED,
    *      InfoObject: 0SALESEMPLY Sales Representative.
            SALESEMPLY           TYPE /BI0/OISALESEMPLY,
    *      InfoObject: 0SUBTOT_1S Subtotal 1 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_1S           TYPE /BI0/OISUBTOT_1S,
    *      InfoObject: 0SUBTOT_2S Subtotal 2 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_2S           TYPE /BI0/OISUBTOT_2S,
    *      InfoObject: 0SUBTOT_3S Subtotal 3 from pricing proced.for conditi
    *on in stat. curr..
            SUBTOT_3S           TYPE /BI0/OISUBTOT_3S,
    *      InfoObject: 0SUBTOT_4S Subtotal 4 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_4S           TYPE /BI0/OISUBTOT_4S,
    *      InfoObject: 0SUBTOT_5S Subtotal 5 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_5S           TYPE /BI0/OISUBTOT_5S,
    *      InfoObject: 0SUBTOT_6S Subtotal 6 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_6S           TYPE /BI0/OISUBTOT_6S,
    *      InfoObject: 0OPORDQTYBM Open orders quantity in base unit of meas
    *ure.
            OPORDQTYBM           TYPE /BI0/OIOPORDQTYBM,
    *      InfoObject: 0OPORDVALSC Net value of open orders in statistics cu
    *rrency.
            OPORDVALSC           TYPE /BI0/OIOPORDVALSC,
    *      InfoObject: 0QUANT_B Quantity in base units of measure.
            QUANT_B           TYPE /BI0/OIQUANT_B,
    *      InfoObject: 0DOCUMENTS No. of docs.
            DOCUMENTS           TYPE /BI0/OIDOCUMENTS,
    *      InfoObject: 0DOC_ITEMS Number of Document Items.
            DOC_ITEMS           TYPE /BI0/OIDOC_ITEMS,
    *      InfoObject: 0NET_VAL_S Net value in statistics currency.
            NET_VAL_S           TYPE /BI0/OINET_VAL_S,
    *      InfoObject: 0COST_VAL_S Cost in statistics currency.
            COST_VAL_S           TYPE /BI0/OICOST_VAL_S,
    *      InfoObject: 0GR_WT_KG Gross weight in kilograms.
            GR_WT_KG           TYPE /BI0/OIGR_WT_KG,
    *      InfoObject: 0NT_WT_KG Net weight in kilograms.
            NT_WT_KG           TYPE /BI0/OINT_WT_KG,
    *      InfoObject: 0VOLUME_CDM Volume in cubic decimeters.
            VOLUME_CDM           TYPE /BI0/OIVOLUME_CDM,
    *      InfoObject: 0HDCNT_LAST Number of Employees.
            HDCNT_LAST           TYPE /BI0/OIHDCNT_LAST,
    *      InfoObject: 0CRM_PROD Product.
            CRM_PROD           TYPE /BI0/OICRM_PROD,
    *      InfoObject: 0CP_CATEG Category.
            CP_CATEG           TYPE /BI0/OICP_CATEG,
    *      InfoObject: 0FISCYEAR Fiscal year.
            FISCYEAR           TYPE /BI0/OIFISCYEAR,
    *      InfoObject: 0BP_GRP BP: Business Partner Group (from Hierarchy).
            BP_GRP           TYPE /BI0/OIBP_GRP,
    *      InfoObject: 0STAT_CURR Statistics Currency.
            STAT_CURR           TYPE /BI0/OISTAT_CURR,
    *      InfoObject: 0BASE_UOM Base Unit of Measure.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
    *      InfoObject: 0PROD_CATEG Product Category.
            PROD_CATEG           TYPE /BI0/OIPROD_CATEG,
    *      InfoObject: 0VOLUME Volume.
            VOLUME           TYPE /BI0/OIVOLUME,
    *      InfoObject: 0VOLUMEUNIT Volume unit.
            VOLUMEUNIT           TYPE /BI0/OIVOLUMEUNIT,
    *      InfoObject: 0FISCPER3 Posting period.
            FISCPER3           TYPE /BI0/OIFISCPER3,
    *      InfoObject: 0SALES_DIST Sales District.
            SALES_DIST           TYPE /BI0/OISALES_DIST,
    *      InfoObject: 0BILL_TYPE Billing type.
            BILL_TYPE           TYPE /BI0/OIBILL_TYPE,
    *      InfoObject: 0MOVE_PLANT Receiving Plant/Issuing Plant.
            MOVE_PLANT           TYPE /BI0/OIMOVE_PLANT,
    *      InfoObject: 0SHIP_COND Shipping conditions.
            SHIP_COND           TYPE /BI0/OISHIP_COND,
    *      InfoObject: 0AB_RFBSK Status for Transfer to Accounting.
            AB_RFBSK           TYPE /BI0/OIAB_RFBSK,
    *      InfoObject: 0AB_FKSTO Indicator: Document Is Cancelled.
            AB_FKSTO           TYPE /BI0/OIAB_FKSTO,
    *      InfoObject: 0CUST_GRP5 Customer Group 5.
            CUST_GRP5           TYPE /BI0/OICUST_GRP5,
    *      InfoObject: ZCU_COND1 Constomer Condition Group 1.
            /BIC/ZCU_COND1           TYPE /BIC/OIZCU_COND1,
    *      InfoObject: ZCU_COND2 Customer Condition Group 2.
            /BIC/ZCU_COND2           TYPE /BIC/OIZCU_COND2,
    *      InfoObject: ZBATCHCD Batch Code.
            /BIC/ZBATCHCD           TYPE /BIC/OIZBATCHCD,
    *      InfoObject: 0BATCH Batch number.
            BATCH           TYPE /BI0/OIBATCH,
    *      InfoObject: ZBATCH Batch number.
            /BIC/ZBATCH           TYPE /BIC/OIZBATCH,
    *      Field: RECORD Data record number.
            RECORD           TYPE RSARECORD,
          END   OF _ty_s_TG_1_full.
    * Additional declaration for update rule interface
      DATA:
        MONITOR       type standard table of rsmonitor  WITH HEADER LINE,
        MONITOR_RECNO type standard table of rsmonitors WITH HEADER LINE,
        RECORD_NO     LIKE SY-TABIX,
        RECORD_ALL    LIKE SY-TABIX,
        SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS.
    * global definitions from update rules
    * TABLES: ...
    DATA: IN    TYPE F,
          OUT   TYPE F,
          DENOM TYPE F,
          NUMER TYPE F.
    * Def. of 'credit-documents': following doc.categ. are 'credit docs'
    *   reversal invoice (N)
    *   credit memo  (O)
    *   internal credit memo (6)
    * Credit-documents are delivered with negative sign. Sign is switched
    * to positive to provide positive key-figures in the cube.
    * The combination of characteristics DE_CRED and DOC-CLASS provides
    * a comfortable way to distinguisch e.g. positive incoming orders or
    * order returns.
    * Def. der 'Soll-Dokumente': folgende Belegtypen sind 'Soll-Belege'
    *   Storno Rechnung (N)
    *   Gutschrift (O)
    *   Interne Verrechn. Gutschr. (6)
    * Soll-Dokumente werden mit negativem Vorzeichen geliefert. Um die Kenn-
    * zahlen positiv in den Cube zu schreiben, wird das Vorzeich. gedreht
    * Die Kombination der Merkmale DEB_CRED und DOC-CLASS gibt Ihnen die
    * Möglichkeit schnell z.B. zwischen Auftrags-Eingang oder Retouren zu
    * unterscheiden.
    DATA: DEB_CRED(3) TYPE C VALUE 'NO6'.
    FORM routine_0002
      TABLES
       P_MONITOR         structure rsmonitor
      CHANGING
        RESULT         TYPE _ty_s_TG_1_full-DOCUMENTS
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    * init variables
    * fill the internal table "MONITOR", to make monitor entries
    CLEAR RESULT.
    RESULT = COMM_STRUCTURE-NO_INV.
    IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
       RESULT = RESULT * ( -1 ).
    ENDIF.
    RETURNCODE = 0.
      p_monitor[] = MONITOR[].
      CLEAR:
        MONITOR[].
    ENDFORM.                    "routine_0002
    FORM routine_0003
      TABLES
       P_MONITOR         structure rsmonitor
      CHANGING
        RESULT         TYPE _ty_s_TG_1_full-DEB_CRED
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    * init variables
    * fill the internal table "MONITOR", to make monitor entries
      IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
        RESULT = 'C'.
      ELSE.
        RESULT = 'D'.
      ENDIF.
      RETURNCODE = 0.
      p_monitor[] = MONITOR[].
      CLEAR:
        MONITOR[].
    ENDFORM.   
    Error:
    E:Field "COMM_STRUCTURE-NO_INV" is unknown. It is neither in one of the
    specified tables nor defined by a "DATA" statement. "DATA" statement.
    communication structure chaged to sours fields but no uses , please suggest how can i proceed , Thanks in Advance immediate replay
    Thanks & Regards
    Ramesh G

    Hi Gareth,
    You have two options:
    1. Transport from BW 3.1 to BI 7.0. You'll need to create a transport route between both systems. This may cause you some troubles in the future when you want to modify the objects you transported.
    2. As there are few objects, you can use XML export utility from Transport connection. There, you make an XML file with the objects you need to transport. One thing that you may take care of, in this option, is that the business content objects you are exporting need to be activated in the destination system. Another problem is that querys are not exported.
    Since it's only a cube, maybe you can create the objects manually. Look that in BI 7.0 there are several new functionalities, i don't know how transport or xml export would work.
    Hope this helps.
    Regards,
    Diego

  • MM data flow

    My dear Friends,
    I want Data flow Co with SD and MM with examples please..
    Amruta.
    Email : - [email protected]

    Hi,
    <b>Link Between SAP SD, MM & FI</b>
    1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD :-
    1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped 
    directly to your customer). 
    1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.
    2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc.                
    <b>The link between SD and MM :-</b>
    1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
    2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
    3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
    4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
    There are many such links between SD and MM.
    <b>Now the link between SD and FI :-</b>
    1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
    Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
    2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
    3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
    SD Integration points with other modules
    SD module is highly integrated with the other modules in SAP.
    Sales Order –
    Integration Points                      Module
    •Availability Check             -       MM
    •Credit Check                   -       FI
    •Costing                        -       CO/ MM
    •Tax Determination              -       FI
    •Transfer of Requirements       -       PP/ MM
    Delivery & Goods Issue –
    Integration Points                      Module
    •Availability Check             -       MM
    •Credit Check                   -       FI
    •Reduces stock                  -       MM
    •Reduces Inventory $            -       FI/ CO
    •Requirement Eliminated         -       PP/ MM
    Billing -
    Integration Points                      Module
    •Debit A/R                      -       FI/ CO
    •Credit Revenue                 -       FI/ CO
    •Updates G/ L                   -       FI/ CO
      (Tax, discounts, surcharges, etc.)
    •Milestone Billing              -       PS
    Return Delivery & Credit Memo -
    Integration Points                      Module
    •Increases Inventory            -       MM
    •Updates G/ L                   -       FI
    •Credit Memo                    -       FI
    •Adjustment to A/R              -       FI
    •Reduces Revenue                -       FI
    SD Transaction Code Flow: 
    Inquiry / Document type IN
    Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP
    Quotation / QT
    Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP
    Purchase Order PO
    Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
    Sales Order OR
    Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP
    Delivery LF
    Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS
    Billing MN
    Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
    To create a sales order we need purchase order number and custmer number.  Before that, to create a purchase order we need to have material no, vendor no.
    To create vendor tcode is 
    xk01(create), xk02(change) , xk03(display)
    Tables are lfa1.
    To create custmer tcode is xd01, xd02, xd03.
    Table is kna1.
    After creating sales order using this no we can create delivery note tcode is vl01.
    Reward if useful.
    Chandru.
    Message was edited by:
            CHANDRAMOHAN NATARAJAN

  • How to make data flow from one application to other in BPEL.

    Hi All,
    I am designing work-flow of my application through BPEL(JDeveloper), I am making different BPEL projects for different functions, like sales manager got the order from sales person and sales manager either approve it or reject it, if he approve it it goes to Production manager and he ships the goods, now I want to keep sales person, sales manger,production manager in seperate BPEL files and want to get the output of sales person to sales manager and sales manager to production manager please help me in dong this.
    I was trying to make partner link in Sales manager of sales person and getting the input from there. I dont know this is right even or not, if it is right I dont know how to make data flow from one application to other.
    Experience people please guide.
    Sales Person -----> Sales Manager ----> Production Manager
    Thanks
    Yatan

    Yes you can do this.
    If you each integration point to be in different process, you have to create three BPEL process.
    1. Create a Async BPEL process 'A' which will be initiated when sales person creates the order.
    2. From BPEL process 'A' call a ASync BPEL process 'B' which has the approval flow. Depending on the input from process 'A' the sales manager will review the order in workflow and approve or reject and send the result back to process 'A'.
    3. Based on the result from workflow, invoke the Sync BPEL process 'C', where you can implement the shipping logic.
    -Ramana.

  • SAP BO Rapidmart for sales: Data loading issue

    I could successfully load data to the sales rapidmart [XI 3.2] from SAP R/3 till QA [Our DEV and QA are same]. I have imported the same ATL to PRD and could succesfuly load 2 months of data. For the subsequent loads, its throwing me the following error.
    11252     8464     DBS-070401     5/31/2010 7:38:40 AM     |Data flow DF_DeliveryFact_SAP|Loader Rename_DELIVERY_FACT
    11252     8464     DBS-070401     5/31/2010 7:38:40 AM     ODBC data source <LIONSAPBI02> error message for operation    <SQLExecute>: <[Microsoft][ODBC SQL Server Driver]Datetime field
    11252     8464     DBS-070401     5/31/2010 7:38:40 AM     overflow>.|<Regular Load Operations>|<DELIVERY_FACT>
    Can  somebody help me in this?

    Hi,
    Refer the lnik and the note mentioned it.
    Re: Problem when storing master data 0PLANT_ATTR-Full (i.e. Full Update)
    With rgds,
    Anil Kumar Sharma .P

  • Required, SD DATA FLOW  with MM Integration.

    Dear Experts,
    I have used the search functionality.. but got links..
    Please Explain in your words, 1.SD Data Flow.
    and also please mention its Integration with MM.
    Points Assured.
    Thanks

    Link Between SAP SD, MM & FI
    The link between SD and MM :-
    1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
    2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
    3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
    4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
    There are many such links between SD and MM.
    Now the link between SD and FI :-
    1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
    Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
    2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
    3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
    SD Integration points with other modules
    SD module is highly integrated with the other modules in SAP.
    Sales Order –
    Integration Points                      Module
    •Availability Check             -       MM
    •Credit Check                   -       FI
    •Costing                        -       CO/ MM
    •Tax Determination              -       FI
    •Transfer of Requirements       -       PP/ MM
    Delivery & Goods Issue –
    Integration Points                      Module
    •Availability Check             -       MM
    •Credit Check                   -       FI
    •Reduces stock                  -       MM
    •Reduces Inventory $            -       FI/ CO
    •Requirement Eliminated         -       PP/ MM
    Billing -
    Integration Points                      Module
    •Debit A/R                      -       FI/ CO
    •Credit Revenue                 -       FI/ CO
    •Updates G/ L                   -       FI/ CO
      (Tax, discounts, surcharges, etc.)
    •Milestone Billing              -       PS
    Return Delivery & Credit Memo -
    Integration Points                      Module
    •Increases Inventory            -       MM
    •Updates G/ L                   -       FI
    •Credit Memo                    -       FI
    •Adjustment to A/R              -       FI
    •Reduces Revenue                -       FI
    SD Transaction Code Flow: 
    Inquiry / Document type IN
    Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP
    Quotation / QT
    Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP
    Sales Order OR
    Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP
    Delivery LF
    Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS
    Billing F2
    Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
    Regards,
    Rajesh Banka
    Reward suitable points.

  • Sales document flow(vbfa) entries are deleted

    Hi Guys,
            I am facing a problem with VBFA table. Actually for some delivery i am able to get Sales order number from VBFA table but for some delivery there is no records exists in VBFA table. So just want to know is there any program or Funtion module which delete entries from VBFA table if not then is there any functional configuration which not allowed to enter data in VBFA table. In my system i searched for all the programs and function module  but no luck.
    I can saw the Sales document flow in VL03N but no entries in VBFA table.
    thanks,
    Baidya

    Hi  Guys,
          Thanks for the replies.
    But this is true for some delivery there is no entries in VBFA table but entries are exist in LIKP and LIPS. We are using userexit in sales order program for creating delivery. The Function module  which creates delivery inside the USER-EXIT is : BAPI_OUTB_DELIVERY_CREATE_SLS.
    If anyone face this type of problem please reply..
    Thanks,
    Baidya

  • Sales document flow table VBFA

    Hi All,
    What exactly the meaning of sales document flow how the data in table VBFA  is filled I mean from which Tcodes this table data will be filled?
    I am calculating the open quantity of a particular sales document which the data (quantity delivered vbfa-rfmng ) I have to take from table VBFA and subtract this from the order quantity(vbap-kwmeng).
    Thanks&Regards
    Mahesh

    Use SE16 see the fields of VBFA.
    Normally the sales document flow is SALES ORDER -> DELIVERY-> INVOICE.
    For a particular case it can be
    SO -> Del -> PGI -> Inv -> SO (Return) -> PGR -> Inv (RE-Type) and so on.
    If we know the document no of any one of them thru VBFA we can get the precceding and the following document.
    Thanks,
    Ashish

  • Data flow model for Master data extraction

    Hello friends,
    I have the following scenario where the report layout looks like this. What would be the data flow model for this example if I'm loading master data from R/3
    KNVV     KNA1     KNVP     KNA1     KNA1     KNVP     KNA1
    VKORG     KATR1     KUNN2     NAME1     KTOKD     KUNNR     NAME1
    Sales Org     BCG     Payer No      Payer Nm     Acc Grp     Sold 2 No     Sold 2 Name
    I would appreciate any help.
    Thanks

    Balaji,
    are you trying to develop a master data IOBJ for the field combination given and want to know how to proceed ?
    Did you check out if the current 0customer master data already has the required fields ?
    otherwise you can
    1. create a view for the master
    2. create a FM for the same and use that as a datasource.
    I would suggest you look at the customer master that comes as part of business content first.
    Arun
    Assign points if useful

Maybe you are looking for

  • Archiving    MM_MATNR

    I am trying to use SARA to Archive material master data records, and I want to know what checks are used to determine if a record is archivable. For example, does it check all transactional sales data to validate that the material is not on any sales

  • How do I back my iPad onto an external hard drive?

    How do I change the destination for the backups on iTunes? I can't use my primary HDD to save files because I'm running dangerously low on space on this computer. However, I do have a 2TB external hard drive.  I'm trying to back up 10 GB of video, wh

  • Email Problem with Mac

    Hi, I am new to FIOS so I hope this is the proper board to post in.  I set up 2 subaccounts for verizon.net email and configured them for my Mac Mail program. Everything worked well for about 2 days, and all of a sudden the Mail program keeps asking

  • VIDEO FILTERS MISSING

    When I try to open a project it appears the followin advise: D:\Mis documentos\Adobe\Premiere Pro\3.0\UTN3.PPJ.prproj Video Filter missing: AE.ADBE Motion Video Filter missing: AE.ADBE Opacity Video Filter missing: AE.ADBE ShadowHighlight What can I

  • Troubleshooting LAN/WAN problems

    Hey guys, What informations are important in a sh interface (port) command to troubleshoot a problem ? What i have to look ? What is the normal and problematic numbers ?