Step by step procedure for copa extraction

hi experts,
            what are the steps involved in copa extraction, please give me step by step procedure for copa extraction.
Thanks,
Rk

Hi Rama Krishna
     COPA STEPS
     SERVER R/3 SERVER  CONTOLLING & PROBALITY ANALYSIS  ENTER COPA WITH T-CODE 9TRANSACTION CODE KEBO)  CREATE (OPERATING CONCERN ; IDEAS (CLICK ON EXCUTE)  ENTER (SHORT TEXT,MEDIUM TEXT,LONG TEXT)  FIELD NAME FROM PERITION ; BURKS  DESLECT SOME VALUE FIELDS  LICK ON CHECK BUTTON  CLICK ON SUMMATIATION LEVEL CLICK ON INFO CATALOG  IT GOES TO ATA SOURE [CUSTOMER VERSION EDIT.  SELECT IN SELECTION , HIDE FIELD  CLICK ON SVE BUTTON  NEXT CLICK ON GENERATE  GO BACK   TO CHECK THE DATA IN COPA DATA SOURCE  T- CODE RSA3 –IMP  DATA SOURCE  1-CO –PA800 STISH  CLICK ON EXTRACTION.
     SERVER BW SYSTEM   GO TO INFO SOURCE YSTEM  SELECT YOUR SOURCE SYSTEM  DOUBLE CLICK ON SOURCE SYSTEM  SELECT BW DATA SOURCE  SAP APPLICATION COMPONENTS  CONTROLLING  PROFITABILITY ANALYSIS  RIGHT CLICK  REPLICATE DATA SOURCES  ELECT COPA DATA SOURCE (R.C)  SELECT REPLICATE DATA SOURCE  DOUBLE CLICK ON DATA SOURES  APPLICATION PROPOSAL  1-CO-PA800 SATISH  CLICK ON TRANSFER BUTTON  YES  PROPOSE TRANSFER RULES  IF WARNING OCCURS SAY CONTINUE  ACTIVATE  GO BACK  CREATE INFO AREA  INFO PROVIDER  CREATE INFO CUBE  INFO SOURCE  1-CO –PA8000SATISH  CREATE UPDATE RULES  GO BACK TO INFO SOURCES  REFERESH  FIND THE 1-CO-PA800  PC ON SOURCE SYSTEM AND CREATE INFO PACKAGE  SCHEDULER  MONITOR.
Regards
Ashwin

Similar Messages

  • How to set Delta for COPA Extraction

    Hi all,
    I want to do generic data source using Function Module for COPA can any one tell how to set the delta what fields i have to fill.
    thanks
    kavitha

    Hi kavitha,
    The easiest way to work out with Function Module is to copy the standard one and modify according to your reqirement.
    The standard one is RSAX_BIW_GET_DATA_SIMPLE .
    Dont forget to copy the Function grp RSAX into a custom defined Grp and Modify the Ranges options as per ur req.
    and in Function module, in Sourcecode and Tables, Do modify the E_T_data with ur Generic datasource ,make sure u also modify the select statements within the sourcecode. If you have an idea on ABAP its really easy to work out.
    And regarding the creation of Datasource.
    this blog may help for the same.
    Generic Extraction via Function Module
    Safety Interval Upper Limit of Delta Selection
    This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
    The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
    Leaving the value blank increases the risk that the system could not extract records arising during extraction.
    Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.
    A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
    For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
    Safety Interval Lower Limit
    This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
    For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
    Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
    these are used to determining the delta in a datasource:
    1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
    2. Calendar day - The field is a DATS8 field which always contains the day of the last change.
    3. Numerical pointer - The field contains another numerical pointer that appears with each new record .
    Regards,
    Anish

  • Step by Step procedure for Integration of B0 with BI 7.0, Portal

    Hi,
    My key concerns include integration with SAP Portal, which I did not find in instalaltion guide.
    Please advice on step by by Procedure for BO with BI 7.0 starting with the right version of BO to be installed.
    1. Which version compatible with BI 7.0 SP 12, LATER TO BE UPGRADED TO sp 16
    2. Source of data will be BI and reports will be using BO.
    3. What are components to be installed
    4. Prerequisites for Integration with BI AND SAP Portal.
    5.Steps for Integration with BI 7.0
    6. Steps for Integration with SAP Portal- Where to get the sample iviews. What to do for connction between Portal and BO - this i didnt find in installation guide
    Thanks,
    Harish

    HI,
    here the items:
    SAP Side:
    - all machines have to be in the same domain
    - BI has to trust the portal
    - BI has to accept SSO tickets
    - EP has to generate SSO tickets
    BusinessObjects:
    - SAP Authentication has to be configured
    - BI system should be configured has default system in the options of the SAP authentication
    - authentication.default parameter in the web.xml for InfoView has to be set to secSAPR3
    - BusinessObjects has to be in the same domain
    EP side:
    - in the system landscape configure the Crystal Enterprise Server Properties for your BI system
    - import the portal iview template that is part of the SAP Integration Kit
    - create a new iView
    Ingo

  • Extractions - Step by Step

    Hi BW Gurus,
    I am new SAP BW and preparing for Interviews.
    Could you pls send me docs for :
    All Extractions in detail Step by Step, how to do it?
    How the project requirement/spec look like ?
    Any other helpful doc?
    Thanks.

    Chek this blogs from Roberto for Logistics Extraction:
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    Also go through this link to know the procedure step by step
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    For LIS and LO Difference
    Drawbacks of LIS  compare to LO
    For COPA extraction
    Adding Fileds to COPA DataSource
    Generic Extraction by FM
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    check this link for inventory
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328

  • COPA Extraction

    Hi Friends,
    Im new2 BI7.
    1)Plz provide detailed info on hw 2 go abt for COPA extraction.
    2)I need 2 make Customer specific Datasources.So plz guide on this
    3)Since my existing Copa reps r frm Report painter/Abap,they just drill down 2 multiple screen,,Is multiple drill down functionality possible in BI?If so plz provide details on hw to make sample drill report.
    4)Wat are the crucial steps to take in Copa extraction.
    Plz provide any links/ppts/pdf's.
    It vll be highly appreciated.
    Thanks & Regards.

    CO-PA:
    CO-PA collects all the OLTP data for calculating contribution margins (Sales, cost of sales, overhead costs)
    CO-PA also has power reporting tools and planning functions however co-pa reporting facility is limited to
              Integrated cross-application reporting concept is not as differentiated as it is in BW.
         OLTP system is optimized for transaction processing and high reporting work load has negative impact on the overall performance of the system.
    Flow of Actual Values:
    During Billing in SD Revenues and Payments are transferred to profitability segments in Profitability Analysis at the same time sales quantities are valuated using standard cost of goods manufactured.
    In Overhead cost controlling primary postings is made to objects in overhead cost controlling and assigned to relevant cost object. Actual cost of goods manufactured also assigned to cost objects and at the same time performing cost centers are credited
    The Production Variances calculated for the cost objects i.e. the difference between the actual cost of the goods manufactured and the standard costs are divided into variance categories and settled to profitability segments (example production orders).
    What are the top products and customers in our different divisions. This is one of the typical questions that can be answered with CO-PA Module.
    Characteristics are the fields in an operating Concern according to which data can be differentiated in Profitability Analysis.
    Each characteristic in an operating concern has a series of valid characteristic values.
    Profitability is a fixed combination of valid characteristic values.
    Characteristics:
    Some Characteristics are predefined in Operating concern like Material, Customer, and Company Code. In addition to these fixed characteristics we can define up to 50 characteristics of our own. In most cases we will be able to satisfy our profitability analysis requirements with between 10 to 20 Characteristics.
    Value Fields:
    Key Figures like revenue, cost of goods sold, overhead costs are stored in value fields.
    Organizational Structure:
    The Value fields and Characteristics that are required to conduct detailed analysis vary from industry to Industry and between Individual Customers.
    In CO-PA we can configure structure of one or more operating concerns in each individual installation.
    An operating concern is an Organizational Structure that groups controlling areas together in the same way controlling areas Groups Company’s together
    Data Base Structures in CO-PA:
    Actual Line Item table:      CE1xxxx
    Plan Line Items: CE2xxxx
    Line Item Contain some information at document level that most cases is too detailed for analysis example  CO-PA Document Number, Sales document Number, Posting date.
    CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
    Actual Line Item table:      CE1xxxx
    Plan Line Items: CE2xxxx
    Line Item Contain some information at document level that most cases is too detailed for analysis example CO-PA Document Number, Sales document Number, Posting date.
    CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
    Segment Table: CE4xxxx
    The Characteristics that describes the market are first separated from the rest of the line Items.
    Each combination of characteristic vales is stored in profitability segment number. The Link between the profitability segment number and characteristic values is maintained in Segment Table.
    Segment Level: CE3xxxx
    The Value fields are summarized at profitability segment and period levels and stored together with these fields in Table CE3xxxx.
    This table contains total values of the period for each Profitability segment number.
    Storage Procedure:
    We can compare an operating Concern associated by segment table and segment level to an Info cube. Info cube comprises Dimension Table Segment Table) and the fact table (Segment Level).
    Unlike Fact table the segment level key contains other keys like processing type in addition to the key field from the segment table.
    Characteristics in Info Cube correspond to characteristics (Or Attributes) in Info Cube.
    Value fields can be regarded as a Key Figures.
    Summarization level in Operating Concern have the same function as aggregates for an Info Cube, the difference is that aggregates for Info Cube are managed together with the Info Cube Itself while summarization levels are updated at regular intervals usually daily.
    Line Items in CO-PA is comparable with Operational Data Store
    Data Staging Overview:
    To Provide Data Source for BW all CO-PA Data Sources must be generated in the Source System.
    Data Sources can be defined at Operating Concern and client level.
    Data Source contains the following Information
    Name of the Operating Concern
    Client
    Subset of the Characteristics
    Subset of the Value fields
    Time Stamp which data has already been loaded in to BW.
    Creating Data Source:
    Since Data Source is always defined at operating concern and Client levels a standard name is always generated which starts with 1_CO_PA_<%CL>_<%ERK . We can change this name if necessary however the prefix 1_CO_PA is Mandatory.
    Data Source-Segment Table:
    Characteristics from the segment table are the characteristics that are maintained in transaction KEQ3.
    By Default all characteristics are selected.
    Data Source-Accounting Base:
    When we generate CO-PA Data Source select accounting based option.
    Fields KOKRS, BUKRS, KSTAR are compulsory.
    There are no Characteristics available for line Items because accounting based data sources do not contain characteristics.
    There are no value fields or calculated key figures available
    KOKRS and PERIO must be selected as selection fields.
    Hope it will helps you........

  • Release procedure for Purchase orders

    Hello SAP Gurus,
    Can anyone explain in steps the release procedure for purchase orders and also can any one explain how it differs from Puchase requisition release procedure.
    Thanks
    NDS

    Hi
    Release procedure for Purchase orders here is process flow.
    Go to spro>img>materials management>purchassing>Release procedure for Purchase orders
    1. Create characterstics  -Intially you will create characterstics based on which you would like to release a purchase order.
    Charactrestics are like plant, purchase order value,purchase group etc.. Assign characterstics to release class 032.
    2. Create Release group say 01 and create release codes like pm(project manager), gm(general manager) etcc..
    3.  Create a Release starategy say s1 and assign release group to it 01 and release class 032 and department to whom this release stategy applies say MM. define the order of release say first pm followed by gm etc..
    4.  under classfication define value limits for release of purchase order.
    5. define release indicators
    6. simulate the release
    7. assign if there is any workflow.
    hope it helps.

  • Difference between LO and COPA Extraction and Steps

    Hello All,
    Can you please share the COPA extraction steps and also advise why COPA is differnt from other extraction (e.g.LIS/LO etc.) mechanisms?
    And also advise what should be my aproach for any COPA extraction related reporting projects.
    Thanks,
    Mainak

    Hi Mainak,
    COPA Extraction -steps
    R/3 System
    1. KEB0
    2. Select Datasource 1_CO_PA_CCA
    3. Select Field Name for Partitioning (Eg, Ccode)
    4. Initialise
    5. Select characteristics & Value Fields & Key Figures
    6. Select Development Class/Local Object
    7. Workbench Request
    8. Edit your Data Source to Select/Hide Fields
    9. Extract Checker at RSA3 & Extract
    BW
    1. Replicate Data Source
    2. Assign Info Source
    3. Transfer all Data Source elements to Info Source
    4. Activate Info Source
    5. Create Cube on Infoprovider (Copy str from Infosource)
    6. Go to Dimensions and create dimensions, Define & Assign
    7. Check & Activate
    8. Create Update Rules
    9. Insert/Modify KF and write routines (const, formula, abap)
    10. Activate
    11. Create InfoPackage for Initialization
    12. Maintain Infopackage
    13. Under Update Tab Select Initialize delta on Infopackage
    14. Schedule/Monitor
    15. Create Another InfoPackage for Delta
    16. Check on DELTA OptionPls r
    17. Ready for Delta Load
    LIS, CO/PA, and FI/SL are Customer Generated Generic Extractors, and LO is BW Content Extractors.
    LIS is a cross application component LIS of SAP R/3 , which includes, Sales Information System, Purchasing Information System, Inventory Controlling....
    Similarly CO/PA and FI/SL are used for specific Application Component of SAP R/3.
    CO/PA collects all the OLTP data for calculating contribution margins (sales, cost of sales, overhead costs).
    FI/SL collects all the OLTP data for financial accounting, special ledger
    Difference: CO-PA / LIS / LO / FI-SL
    1)Method for Delta: Time Stamp / LIS InfoStructure / Change Log / PseudoDelta
    2) Application Specific: All are
    3) Extractors: Customer Generated (CG) / SAP BW Content / CG / CG
    4) Tables Used: Line item tables / 1 structure (s5nn). 2 tables (BWl1 and 2) and control change log (TMCBIW) / V3 update(asynchronous) and two tables: VBDATA and ARCFC (change log from SAP R-3 / Three types of tables - Line Item Tables- ZZP(plan) & ZZA(actual), - Total Table ZZT, - Objects Tables ZZO & ZZC
    Pls refer:
    http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/how%20to%20set%20up%20connection%20co-pa%20-%20extraction
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/how%20to%20set%20up%20connection%20co-pa%20-%20retraction
    Differences between LIS,LO,CO/PA and FI-SL extractors
    *Pls   Assign points if  info is useful*
    Regards
    CSM Reddy

  • Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

    Hi ,
    Can any body provide me the step-by-step procedure for Inbound IDOCS.
    As i'm new to this i need the the clarification between Inbound & outbound idocs.
    How can we differentiate both?
    where to define outbound & where to define Inbound?
    ( If possible Please explain me the procedure for  Vendor Create through INBOUND IDOCS )
    Thanks in advance..

    Hi,
    Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    Over view of IDocs:
    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Process flow for Distributing Transactional Data:
    Transactional data is distributed using two techniques: with Message control and without message control.
    Process flow for Distributing Master Data:
    Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
    Triggering the Outbound Process via Stand-Alone Programs:
    Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
    The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
    Triggering the Outbound Process via Change Pointers:
    The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
    A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
    Processing in the Application Layer:
    The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
    Processing in the ALE Interface Layer:
    Processing in the ALE Layer consists of the following steps:
    u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
    u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
    u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
    u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
    u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
    u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
    u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
    u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
    u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
    Processing in the Communication Layer:
    To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
    Inbound Process in IDocs:
    An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
    Posting Program:
    Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
    Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
    Workflow:
    A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
    Partner Profile;
    A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
    Process flow for the Inbound process via a Function Module:
    In this process, IDocs are received from another system and passed to the posting function module directly.
    1. Processing in the communication Layer:
    The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
    2. Processing in the ALE/EDI Interface Layer:
    u2022 Basic integrity check: A basic integrity check is performed on the control record.
    u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
    u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
    u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
    u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
    3. Processing in the Posting Module:
    The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
    The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

  • Is there a Step By Step download procedure for CS4??

    Wondering if there is a step by step procedure for downloading CS4 from the Adobe site??
    Yes- I have tried the following link,  http://kb2.adobe.com/cps/402/kb402065.html  
    however, what folder is best to download it too??
    It also says that both the EXE file and the 7z file must be in the same folder to operate the download.
    Which folder gets opened first after download? Where are the the above files located? Does the EXE go into the same folder as the 7z file or the other way around??
    Most of the FAQ is centered around Akamai... I have removed my anti-spy programs completely and turned off Macafee.
    The download FAQ does not address a step by step procedure. Anyone know if Adobe has one??

    Now, I have not downloaded any Adobe programs, but for the rest, I download to a special folder in my C:\Download Files for each program. I then will Extract with full folder structure to a sub-folder beneath that program's folder. I will install from there, with all AV, pop-up blockers and spy sweepers off.
    Tom's suggestion seems to be a good one for Adobe programs. though I have not use that path - remember, I am NOT downloading and installing any Adobe programs. Still, many have expressed full success with Tom's location.
    Be sure that you ARE logged-in as an Administrator. This is very important to most Adobe programs. Also, allow the installation to locate on your C:\. I do choose C:\Adobe, and not the default C:\Program Files\Adobe, but that is just the way that I manage my Adobe programs. Default is fine.
    Good luck, and do NOT forget to Extract with full folder structure for the installation.
    Hunt

  • Step by Step for FICO(GL,Assets and CO) Extraction

    Hi gurus,
    I am trying to see if i can get a step by step extraction process for FICO extraction cos am abt to start a project to extract and load GL,Asset and Controlling data into a BW system.I am thinking I shd be able to get a lot of the reports needed by installing the 0FI_GL_4.
    Please any help will be appreciated and points will be awarded as well.

    please search the forum before you post a thread, there are lot of threads discussing the same topic.
    coming to steps in extraction:
    install DS
    replicate DS
    create transformation between the DS and DSO
    the same applies to DSO and cube.
    But most of the times, no delivered DS supplements the clients finacial requirement, so if thats the case you would need to enhance the DS with the additional fields that would be needed in the reporting stand point

  • Step by Step document on Guided Procedures for Benefits.......Help Needed..

    Hello Gurus,
    We are in process of implementing Benefits and for which we are using Guided Procedures, want to have understanding of the process can you please provide the step by step documentation and an example process that will be of great help.
    Appreciate your help.
    Thanks in advance for your time.
    Kind Regards,
    Pramod

    Hi Pramod,
    Please have a look at the below links. You will probably get some help.
    First of all, see the following thread, see the answer by shen peng in the end, explained CAF in very simple terms:
    https://www.sdn.sap.com/irj/sdn/thread?threadID=470956&tstart=0
    Now have a look at the following links for understanding about CAF, :
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4277f37b-0601-0010-0597-89e792177e2b">Creating Composite Applications with SAP CAF</a>
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84df3e36-0301-0010-be9d-b99aad8c81e6">Composite Application Framework in SAP NetWeaver</a>
    <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1122">CAF training material online</a>
    <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1231">Additional CAF Training material online</a>
    See the following links for understanding CAF GP in detail:
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0b1c2eda-0c01-0010-b597-b107502cdc71">CAF Guided Procedures Overview</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/39/198141f906040de10000000a1550b0/frameset.htm">CAF Guided Procedures</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/c7/984942da51690de10000000a155106/frameset.htm">Concepts of the Guided Procedures Framework</a>
    Lastly, see the following links for CAF GP Wiki Home Page and CAF Tutorial Center:
    <a href="https://wiki.sdn.sap.com/wiki/display/BPX/Guided+Procedures">CAF Guided Procedures Wiki Home Page</a>
    <a href="https://www.sdn.sap.com/irj/sdn/nw-composition?rid=/webcontent/uuid/d8dbd703-0801-0010-c9bf-c04bc52f562f">Composite Application Framework Tutorial Center</a>
    You can also have a look at the following thread, you can drill down into many more links:
    https://www.sdn.sap.com/irj/sdn/thread?threadID=405517&tstart=0
    https://www.sdn.sap.com/irj/sdn/thread?threadID=314804&tstart=50
    Bye
    Ankur

  • TDMS 3.0 for ERP 6.0:  step by step procedure for  TDSH6 Shell creation

    Dear All,
    I need to perform shell creation. I have never done this and need help with step by step instructions.
    I need to refresh my my development system with a TDMS shell creation from production client in production system.
    I am familiar with TDTIM and performed many TDTIM copies. I have gone throught the master and operational guides for TDMS also.
    I would try to list down my understanding so far after reading the guides.
    Please correct me if I am wrong ang also suggest correct steps.
    1. All my three systems (central, sender and receiver) are ready from installation point of with with authorizations and latest SPs.
    2. I log into Central/Control system and start a new package  "ERP Shell creation package for AP Release higher 4.6 "
    3. AS I have never executed this option I do not know what are the stps inside it.
       But I assume I should be asked for the source client details from which shell needs to be creates. (000 or pruduction client)
       What type of shell  : slave or master?
    4. During the shell creation from sender system client, is there a downtime for sender system.
    5. Once the shell creation is done an export dump will created.
    6. I perform all the preprocessing steps of a homogenous system copy on the receiver systems.
    7. Stop receiver system, start sapinst  database instance installation with homogenous system copy with R3load option.
    8. Provide the export dump location to sapinst.
    9. After database instance is installed, perform system copy specific post processing steps.
    10. Afte the system is ready it has only one client 000 now available in development system and  i need to create a new cleint from 000 which will act as my new development cleint.
    I request all you experts to please provide your comments at the earliest as activity would be starting from 5th of this month.
    Regards,
    Prateek.

    Hi,
    Let me answer your questions.
    Some queries
    1. Is there a downtime for Production system (sender system).
       SAP recommends that nothing much should be going on during the export of the Sender(PRoduction) system, but so far i have never encountered an issue doing the export in online mode.
    2. Shell creation works on both Production and 000 client or only Production client,
       Be carefull!!! - A Shellcreation is a normal Homogenous Systemcopy using R3load. You will create a 'new' system with the DDIC and clientindependent customization of the Sender system. ALL former data of the target system will be deleted.
    You mention that you will refresh a development system that way. Please be aware of the implications that a development refresh contains. That said. After the refresh you will have the 000 client and parts (users ... authorizations of sonder) of the other clients on the new system.
    3. when I import the the dump using sapinst, how many clients are available in receiver systems.
    See above. All client configuration will be available, but nearly no data will be in these clients except 000. A manual part of the Shellcreation is to clean up the target system (delete the clients that are not needed) This is a fast process.
    4. Soem where in the guide it is mentioned that downtime depends on the type of shell I create.
    Kindly suggest should I create a master shell or slave.
    Hm. The master shell is just a concept that you create a complete new system and put that system into your transport landscape without filling it with data. You can then use that system as the source for a normal (database dependent) systemcopy without impacting your prod system. The result is a very small copy that can be repeated very often without an impact to prod/QA...
    Downtime is as described in point1 not required
    5. Once I execute this activity of shell creation for lets say receiver system A, then can I use the same export dump for second receiver system B.
    Yes
    6. Lastly please suggest the activity execution time as customer has provided us 2 days to execute this activity.
    This depends on your knowledge of homogenuous systemcopies and the preparation + some items like size of stxl  and other tables that will be exported/imported.  If you are very familiar with the systemcopy process using R3Load 2 days are feasable.
    I have seen shellcreations done within 1-2 days but also much longer ones!
    As a prerequisite i would always recommedn to have the latest R3* + migmon exe available on sender + target.
    I hope i have clarified some of your items.
    Best Regards
    Joerg

  • Steps for Data extraction from SAP r/3

    Dear all,
    I am New to SAP Bw.
    I have done data extraction from Excel into SAP BW system.
    that is like
    Create info objects > info area> Catalog
                                                --> Character catalog
                                                --> Key catalog
    Create info source
    Upload data.
    create info cube
    I need similar steps for data extraction for SAP R/3
    1. when data is in Ztables ( using Views/Infosets/Function etc)
    2. When data is with Standard SAP using Business Content.
    Thanks and Regards,
    Gaurav Sood

    hi,
    chk the links
    Generic Extraction
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    CO-PA
    http://help.sap.com/saphelp_46c/helpdata/en/7a/4c37ef4a0111d1894c0000e829fbbd/content.htm
    CO-PC
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6
    iNVENTORY
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Extractions in BI
    https://www.sdn.sap.com/irj/sdn/wiki
    LO Extraction:
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    Remya

  • Step by step procedure for Upgrade to ECC6.0

    Hi,
    I gained a lot from this forum . Can someone please mail me at
    [email protected]
    step by step procedure for upgrade .
    Will award full points for helpful documents..
    With regards,
    Mrinal

    SAP defined a roadmap for upgrade.
    1) Project Preparation
    Analyze the actual situation
    Define the objectives
    Create the project plan
    Carry out organizational preparation for example identify the project team
    2)Upgrade Blueprint
    The system and components affected
    The mapped business processes
    The requirements regarding business data
    3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.
    4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning
    5)Production Cutover and Support
    The production solution upgrade
    Startup of the solutions in the new release
    Post processing activities
    Solving typical problems during the initial operation phase.
    SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.
    STEPS IN TECHNICAL UPGRADE
    •     Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
    •     Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
    •     After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified.  This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
    •     Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
    •     Then we need to move Z/Y Objects.  Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
    The main Category of Objects that needs to be Upgraded is –
    •     Includes
    •     Function Groups / Function Modules
    •     Programs / Reports
    •     OSS Notes
    •     SAP Repository Objects
    •     SAP Data Dictionary Objects
    •     Domains, Data Elements
    •     Tables, Structures and Views
    •     Module Pools, Sub Routine pools
    •     BDC Programs
    •     Print Programs
    •     SAP Scripts, Screens
    •     User Exits
    Also refer to the links -
    http://service.sap.com
    http://solutionbrowser.erp.sap.fmpmedia.com/
    http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
    Hope this helps you.

  • Step By step procedures  for various scenarios Required ASAP!!!!!

    Hi All,
    Pls mail me the step by step procedure of the following scenaios.
    1.) File-XI-File Scenario.
    2.) Text file scenario.
    3.)File to Idoc
    4.)File XI- RFC.(R/3)
    5.) BPM scenarios.
    any stuff related pls mail to [email protected]
    Thanks in Advance.
    Sofia.

    Hi Sofia,
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 - File to JDBC
    /people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1 - File to File Part 1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2 - File to File Part 2
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - File to RFC
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken] [original link is broken] - File to Mail
    BPM Scenarios:-
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    Regards.
    Praveen

Maybe you are looking for

  • Google wont work

    when i visit google.com it says "Oops! Google Chrome could not connect to www.google.com" it happened about a weak after i upgraded to lion so i dont think it is lion, i have try'd playing with the security but nothing helps. if anyone has any ideas

  • My iPad with this security code and forgot it,how can I get him ?  Is that 4 digit code

    my iPad with this security code and forgot it,how can I get him ?  Is that 4 digit code.

  • Activate or deactivate a mask in a psd

    hello! sorry for my english :S indesign can enable or disable a layer mask from a psd? withoutcreating two similar layers, one with a mask and one without a mask, to show the masked area outside the image. for example: Final result: two overlapping i

  • IOS - local user privileges

    Hi Experts, I have requirement to create multiple users with different level of permission. Requirement is user with low permission can only execute following commands and no other commands: "show interface fastether1/3" "show ip ospf neighbor" "rout

  • CS3 Tab key all of a sudden is not working but instead removing palettes

    I am working on a long document that came out of Excel. Everything was fine but I have to add an extra tab before the text in the same place in that column. All of sudden, my tab key just gets rid of all my windows/palettes or brings them back and th