PSA & Idoc

Hi all,
Can u give me an idea of these two Transfer methods..
I mean when to use PSA and when to use Idoc...What is the diff.?
How can I see the data in Idocs if I go with the Idoc transfer method?
  can u explain me in project point of view..

Hi Indira,
In PSA, the number of fields is limited to a maximum of 255 when using TRFCs to transfer data. The length of the data record is limited to 1962 bytes when you use TRFCs.
If you are uploading data using IDOC make note of 1000 byte limit per data record .
DAta sources with the IDOC transfer method are not supported with ODS object.
you can only create start routine for transfer method - PSA.
In contrast to a data request with IDocs, a data request in the PSA also gives you various options for a further update of the data in the data targets.
Have a look at these help.sap links
http://help.sap.com/saphelp_nw04/helpdata/en/72/31823cdcf5f354e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/de/113037530b7774e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/b0/ab8e3cb4340b14e10000000a114084/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/b8/5b723b9b4f8f7de10000000a114084/content.htm
Hope this Helps...Let me know
Regards,
R.Ravi

Similar Messages

  • Transfer Methods...PSA & IDoc

    Hi Friends,
    Could you guys share your valuable ideas when we were doing data load at the Transfer structure level could see their Transfer method as PSA & IDOC.
    When we would prefer PSA & When we go for the IDOC.
    Can you guys give any business scenarios?
    Siri

    Hi,
    you want to load Master data text
    If it is a critical data we can use IDocs because data can't be modified here. In case the load fails while using Idcos we need to load data from source system again.
    Generally IDocs update is used to load master data hierachies.
    Some of the other differences are
    PSA
    Data is staged at PSA. From here we can either update the data automatically or manually in the corresponding data targets.
    Incase of PSA the length of data record can be upto 1962 where as Idoc it is 1000bytes max.
    you have advantage of performance ,large data package and error handling in PSA.
    Data transfer with IDoc
    The data is packed into IDocs by the source system and sent to the Business Information Warehouse. In BW your data is saved persistently and intransparently in the IDoc store. From there the IDocs can be updated in the IDocs manually or automatically.
    It is used for hierarchies load Limitations with IDoc is:
    transfer structure must not have more than 1000 Bytes in the character format.
    If it is a critical data we can use IDocs it can't be modified here. In case the load fails we need to load data from source system.
    http://help.sap.com/saphelp_nw04/helpdata/en/7d/724d3caa70ea6fe10000000a114084/frameset.htm

  • DIFFERENCE BETWEEN PSA & IDOc

    Hello Friends,
    Please provide details between PSA& IDOc .
    With regards
    YADAV.T.TT

    Dear Thukaram,
    The following update types are available in SAP BW:
    1. PSA
    2. ALE (data IDoc) 
    You determine the PSA or IDoc transfer method in the transfer rule maintenance screen. The process for loading the data for both transfer methods is triggered by a request IDoc to the source system. Info IDocs are used in both transfer methods. Info IDocs are transferred exclusively using ALE
    A data IDoc consists of a control record, a data record, and a status record The control record contains, for example, administrative information such as the receiver, the sender, and the client. The status record describes the status of the IDoc, for example, "Processed".  If you use the PSA for data extraction, you benefit from increased flexiblity (treatment of incorrect data records). Since you are storing the data temporarily in the PSA before updating it in to the data targets, you can check the data and change it if necessary. Unlike a data request with IDocs, the PSA gives you various options for additional data updates into data targets:
    InfoObject/Data Target Only - This option means that the PSA is not used as a temporary store. You choose this update type if you do not want to check the source system data for consistency and accuracy, or you have already checked this yourself and are sure that you no longer require this data since you are not going to change the structure of the data target again.
    PSA and InfoObject/Data Target in Parallel (Package by Package) - BW receives the data from the source system, writes the data to the PSA and at the same time starts the update into the relevant data targets.  Therefore, this method has the best performance.
    The parallel update is described in detail in the following: A dialog process is started by   data package, in which the data of this package is writtein into the PSA table. If the data is posted successfully into the PSA table, the system releases a second, parallel dialog process that writes the data to the data targets. In this dialog process the transfer rules for the data records of the data package are applied, that data is transferred to the communcation structure, and then written to the data targets. The first dialog process (data posting into the PSA) confirms in the source system that is it completed and the source system sends a new data package to BW while the second dialog process is still updating the data into the data targets.
    The parallelism relates to the data packages, that is, the system writes the data packages into the PSA table and into the data targets in parallel.  Caution: The maximum number of processes setin the source system in customizing for the extractors does not restrict the number of processes in BW. Therefore, BW can require many dialog processes for the load process. Ensure that there are enough dialog processes available in the BW system. If there are not enough processes on the system side, errors occur. Therefore, this method is the least recommended. 
    PSA and then into InfoObject/Data Targets (Package by Package) - Updates data in series into the PSA table and into the data targets by data package. The system starts one process that writes the data packages into the PSA table. Once the data is posted successfuly into the PSA table, it is then written to the data targets in the same dialog process. Updating in series gives you more control over the overall data flow when compared to parallel data transfer since there is only one process per data package in BW. In the BW system the maximum number of dialog process required for each data request corresponds to the setting that you made in customizing for the extractors in the control parameter maintenance screen. In contrast to the parallel update, the system confirms that the process is completed only after the data has been updated into the PSA and also into the data targets for the first data package.
    Only PSA - The data is not posted further from the PSA table immediately. It is useful to transfer the data only into the PSA table if you want to check its accuracy and consistency and, if necessary, modify the data. You then have the following options for updating data from the PSA table:
    Automatic update - In order to update the data automatically in the relevant data target after all data packages are in the PSA table and updated successfully there, in the scheduler when you schedule the InfoPackage, choose Update Subsequently in Data Targets on the Processing tab page.
    Do let me know in case of any queries.
    Hope this helps you.
    Regards,
    Rakesh

  • ALE and IDOC Delta loads

    ALE Delta is used for all Master data delta extracts and referencing change pointer tables
    IDOC Delta Loads are used for transactional delta and access source system queues
    Are the above statements correct? Thanks

    Nitesh
    As you know there are two types of Transfer Methods (PSA & IDOC). Info Idoc are used for both the types of Transfer Methods. Only ALE is used to transfer InfoIDocs.
    The Transfer Method only determine how the data is transfered.
    IN PSA Transfer Method Trfc is used to transfer data directly from Source system to BW.
    Thanks
    Sat

  • Regarding BW Cerification

    Hi There,
    I am planning to appear for BW Certification.
    can some one guide me how to start for preparing certification and what are the books i need to refer for that for that.
    Thanks,
    -Saloni

    Hi Saloni,
    'Step by Step guide on BW' and 'Mastering the SAP Business Information Warehouse' which might be handy.
    Other than those books you also have the following books which can provide good amount knowledge:
    1. Business Information Warehouse for SAP by Naeem Hashmi
    2. SAP BW Certification, A Business Warehouse Sutdy Guide, by Catherine.M.Roze
    Technical Consultant Certification
    SAP NetWeaver´04 - Business Intelligence Sol. Cons. (BW 3.5)
    Exam Content & Weighting Information:
    The certification test consists of questions from the areas specified below:
    1. Reporting (+++)
    - InfoProviders and InfoObjects
    - Document Integration
    - Business Content
    - Report/Report Interface
    Business Explorer
    - The BEx Browser
    - BEx Query Designer
    - BEx Map
    - Analysis and Reporting in the BEx Analyzer
    - Mobile Reporting
    - Bex Web Application Designer
    - Internet Graphics Server (IGS)
    Query Designer
    - Calculated and Restricted Key Figures
    - Properties of Key Figures
    - Navigation
    - Characteristics
    - Properties and Attributes
    - Hierarchies
    - Query Properties
    - Variables
    - Exceptions and Conditions
    Reporting Agent
    - Exceptions
    - Printing
    - Additional Functions
    - Pre-Calculating Web Templates
    Bex Web Application Designer
    - Web Items
    - Context Menu
    - Structuring the Layout of Web Templates
    - Cascading Stylesheets
    - Chart Designer
    - Web Analyzer
    Ad-hoc Query Designer
    Analysis Process Designer (APD)
    2. Business Planning and Simulation (++)
    - General concepts and challenges of business planning
    - Positioning of BPS and relationship to BW
    - Set up of planning structures
    - Manual planning and layout formatting
    - Locking concept and commit model used in BPS
    - Configuration of planning functions and sequences
    - Definition and usage of variables
    - Design of end user interfaces using planning folders and the Web Interface Builder
    - Authorization concept and options for data models
    - Integration of hierarchies and attributes into BPS
    - Characteristic relationships for deriving and validating data
    - Tools and tips for performance analysis and optimization
    - Options for system landscapes
    - Retraction of data into SAP R/3 applications
    - Status and Tracking System
    3. Data Modeling (++)
    - InfoProviders
    - Using Different InfoProvider Types
    - MultiProviders
    Characteristics/attributes
    - Navigation Attributes
    - Status Attributes
    Tracking History
    Dimensions
    - Structure of Dimension Tables
    - Dimension Modeling
    - BW Star Schema
    4. Warehouse Management (+++)
    - Administrator Workbench Functions
    - Scheduler
    - Process Chains
    - Monitor
    - Source Systems
    - BW Statistics
    InfoObject Within BW
    - Definition
    - Texts, Attributes, Hierarchies
    - Compounded InfoObjects
    Data Flow in BW
    - Involved Objects
    - Transfer Rules
    - Update Rules
    Business Content
    - Definition
    - Activation
    Storing Data in BW
    - Data Targets
    - Types
    - Architecture
    - Data Target - Administration
    - Aggregate Maintenance
    Metadata Repository
    - Architecture
    - Functionality
    5. Extraction (++)
    - Data Flow
    Extraction from SAP Source Systems
    - Transfer Methods (PSA(Idoc)
    - DataSources
    - Extraction from CO-PA
    Creating a DataSource
    Data Transfer
    - Data Extraction Logistics
    LO Cockpit Functions
    LO DataSources Data Flow in R/3
    Structure of Delta Method for LO Cockpit DataSources
    - Connecting LIS InfoStructures to SAP BW
    - Delta Method for DataSources to LIS InfoStructures
    - Delta Management for Transaction Data
    Delta Method
    Delta Method Components
    Delta Queue Functions
    - Generic Extraction
    Data Types
    Data Sources
    - Enhancing Business Content
    Extraction with Flat Files
    - Extracting Transaction and Master Data using Flat Files
    - Data Types that Can be Extracted using Flat Files
    DB Connect
    Universal Data Integration
    XML Integration
    DataMart Interface
    Virtual InfoCubes
    6. Authorizations
    Administration
    - Authorization Object Classes
    - Authorization Objects
    - Authorizations
    The Authorization Concept
    - Roles
    - Reporting User
    - Warehouse Management User
    7. SAP NetWeaver 04 - Technical Scenarios (++)
    - Information Broadcasting
    BW Information Broadcasting: Overview and Positioning
    BEx Broadcaster Functions
    Setting up Events, Time Points and Authorizations
    Workbook Precalculation
    - SAP BW and SAP Enterprise Portal (EP 6.0) Integration
    - SAP BW and SAP XI Integration
    - SAP BW and SAP MDM Integration
    - BW Alerts in the Central Alert Framework (SAP Web Application Server)
    - Web Services
    Weighting key in the test:
    + = 1 - 9%
    ++ = 10 - 19%
    +++ = over 20%
    No responsibility is taken for the correctness of this information. Copyright © SAP AG 2004.
    see if this helps -
    https://websmp101.sap-ag.de/~sapidp/011000358700007394712005E
    Please go through the following thread
    1. Read Datawarehousing books written by Kimbal or Inmon to familiarize yourself with the basic concepts.
    2. Follow the SAP training on BW Data Warehousing, BW Reporting and BW Modeling (there are SAP press books that can help with this)
    3. Business Information Warehouse Study Guide (Paperback)
    by Catherine M. Roze
    4.There is also SAP BW Professional Training by Norbert Egger that is a good one.
    . Try to grab a little bit of ABAP. Horst Keller book (ABAP Objects) can help.
    explore this -
    http://www.sap-press.com/product.cfm?account=&product=H1918
    and look for BW books.
    /people/gilad.weinbach2/blog/2007/02/23/a-beginners-guide-to-your-first-bi-model-in-nw2004s
    Hope this helps.
    ****Assign Points If Helpful***
    Regards,
    Ravikanth

  • BW certification

    i all,
    i am planning to do BW certification .
    i am not much conversant with the process and procedure.
    i would appreciate if anyone can help me on the below mentioned questions.
    1) from where can i get the training material, if anyone has it please mail it to me at [email protected]
    2) has anyone  undergone any training related to BW, then from where?. I enquired with genovate(mumbai) and they told me that they dont conduct trainings related to SAP BW and they asked me to contact  SAP india, though from many of my friends i have heard that genovate conducts SAP related trainings.
    can anyone please give me details of some recognised institute which offers BW trainings in Mumbai.
    3) have i to first get certified on BW 3.0 and then i can get certified on 3.5?
    4) what are the carrier prospects of the BW consultant. I mean are there bright oppurtunities for a BW consultant. Is it a rear skill.?
    5) how much would be the cost for the certification ? (in india)
    thanks in advance
    Ramesh

    Hi Ramesh,
    As of now only BW3.5 certification is availbale. BI 7.0 would be offered next year. The topics for the exam are as follows and the weightage is also mentioned. You can concentrate on the areas which have good weightage first.
    SAP Consultant Certification
    Solution Consultant SAP NetWeaver ‘04 – Business Intelligence
    Software components: SAP BW 3.5
    Certification exam is included in course TBW45 and is also offered separately at many SAP locations.
    Certification ID (Booking code): C_TBW45_04
    Certification duration: 3 hours
    Number of certification questions: 80
    Required certificates for participation in this certification test:: None
    Courses for certification preparation: TBW10, TBW20, TBW30, TBW40, TBW45
    Please note that you are not allowed to use any reference materials during the certification test (no access to online documentation or to any SAP system).
    The certification test Solution Consultant SAP NetWeaver ‘04 – Business Intelligence verifies the knowledge in the area of the SAP NetWeaver for the consultant profile Business Intelligence. This certificate proves that the candidate has a basic understanding within this consultant profile, and can implement this knowledge practically in projects.
    The certification test consists of questions from the areas specified below:
    Topic Areas
    1. Reporting (+++)
    InfoProviders and InfoObjects
    Document Integration
    Business Content
    Report/Report Interface
    Business Explorer
    The BEx Browser
    BEx Query Designer
    BEx Map
    Analysis and Reporting in the BEx Analyzer
    Mobile Reporting
    Bex Web Application Designer
    Internet Graphics Server (IGS)
    Query Designer
    Calculated and Restricted Key Figures
    Properties of Key Figures
    Navigation
    Characteristics
    Properties and Attributes
    Hierarchies
    Query Properties
    Variables
    Exceptions and Conditions
    Reporting Agent
    Exceptions
    Printing
    Additional Functions
    Pre-Calculating Web Templates
    Bex Web Application Designer
    Web Items
    Context Menu
    Structuring the Layout of Web Templates
    Cascading Stylesheets
    Chart Designer
    Web Analyzer
    Ad-hoc Query Designer
    2. Business Planning and Simulation (++)
    General concepts and challenges of business planning
    Positioning of BPS and relationship to BW
    Set up of planning structures
    Manual planning and layout formatting
    Locking concept and commit model used in BPS
    Configuration of planning functions and sequences
    Definition and usage of variables
    Design of end user interfaces using planning folders and the Web Interface Builder
    Options for data models
    Integration of hierarchies and attributes into BPS
    Characteristic relationships for deriving and validating data
    Status and Tracking System
    3. Data Modeling (++)
    InfoProviders
    Using Different InfoProvider Types
    MultiProviders
    Characteristics/attributes
    Navigation Attributes
    Status Attributes
    Tracking History
    Dimensions
    Structure of Dimension Tables
    Dimension Modeling
    BW Star Schema
    4. Warehouse Management (+++)
    Administrator Workbench Functions
    Scheduler
    Process Chains
    Monitor
    Source Systems
    BW Statistics
    InfoObject Within BW
    Definition
    Texts, Attributes, Hierarchies
    Compounded InfoObjects
    Data Flow in BW
    Involved Objects
    Transfer Rules
    Update Rules
    Business Content
    Definition
    Activation
    Storing Data in BW
    Data Targets
    Types
    Architecture
    Data Target - Administration
    Aggregate Maintenance
    Metadata Repository
    Architecture
    Functionality
    5. Extraction (++)
    Data Flow
    Extraction from SAP Source Systems
    Transfer Methods (PSA(Idoc)
    DataSources
    Data Extraction Logistics
    - LO Cockpit Functions
    - LO DataSources Data Flow in R/3
    - Structure of Delta Method for LO Cockpit DataSources
    Delta Management in extraction
    - Delta Method
    - Delta Method Properties
    - Delta Queue Functions
    Generic Extraction
    - Data Types
    - Data Sources
    Enhancing Business Content
    Extraction with Flat Files
    Extracting Transaction and Master Data using Flat Files
    Data Types that Can be Extracted using Flat Files
    DB Connect
    Universal Data Integration
    XML Integration
    DataMart Interface
    Open Hub Service
    Virtual InfoCubes
    6. Authorizations
    Administration
    Authorization Object Classes
    Authorization Objects
    Authorizations
    The Authorization Concept
    Roles
    Reporting User
    Warehouse Management User
    7. SAP NetWeaver 04 - Technical Scenarios (++)
    Information Broadcasting
    BW Information Broadcasting: Overview and Positioning
    BEx Broadcaster Functions
    Setting up Events, Time Points and Authorizations
    Workbook Precalculation
    SAP BW and SAP Enterprise Portal (EP 6.0) Integration
    SAP BW and SAP XI Integration
    BW Alerts in the Central Alert Framework (SAP Web Application Server)
    Web Services
    Weighting key in the test:
    + = 1 - 9%
    ++ = 10 - 19%
    +++ = over 20%
    No responsibility is taken for the correctness of this information. Copyright © SAP AG 2004.
    Bye
    Dinesh

  • Transfer Method in transfer rules

    Dear All,
               If I make an infosource and assign data source go to " change transfer rules". I get 2 radiobutton options in "transfer method"....PSA or IDOC. What is this? How does it affect the flow of data? and how is it different from the options I get in infopackage?
    Regards,
    Ratish
    [email protected]

    Hi Ratish,
       The two data transfer methods are PSA and IDoc. In PSA, the number of fields is limited to a maximum of 255 when using TRFCs to transfer data. The length of the data record is limited to 1962 bytes when you use TRFCs.
    If u choose PSA as the transfer method, staging of data can be possible.It stores the exact replica of the data from the source system.In case if the load fails, you can retrive data from the psa through manual update or reconstruction.
    And also editing can be done in psa.
    where as in IDOC error handling is not possible. In requirements where security plays major role we use this type of transfer method, where no one can edit the information.But when the load fails we have to run the load again from the source system.
    Refer help link
    http://help.sap.com/saphelp_nw04/helpdata/en/7d/724d3caa70ea6fe10000000a114084/frameset.htm
    TRANSFER METHOD IN THE INFOSOURCE? PSA/IDOC
    regards
    @jay

  • Infopackage "transfer method"

    Hello - of the 2 types of transfers methods, IDOC and PSA, it's my understanding that the PSA one is recommended in almost all cases (except possibly in some hierarchy type loads where IDOC may be the only option).  and this is because the PSA option is the only option that utilizes the more efficient, TRFC, technology.
    i'm trying to get a little more technical clarification here between the 2 types of transfer methods.
    1) do both types still use IDOC's to some extent?  (it's my understanding PSA will send "data packets and info-idoc's"; whereas the IDOC method will send data via ALE and traditional IDOC technology (data IDOC's, and status/info IDOC's).
    2) do the ROIDOCPRMS settings "only" affect things if the PSA transfer method is used?
    3) the ROIDOCPRMS-FREQUENCY setting is defined as the "# of data idoc's that an info idoc describes" - this makes it sound like PSA transfer method will send data (i'm talking here of the real data, not the status/info type data) via data idoc's and not via "packets".  true/false?
    are there "data" idoc's sent w/ both types of transfer methods (PSA & IDOC)?

    ALSO:  it's my understanding, that w/ the PSA transfer method, that the "info" idoc's involved there provide for the "traffic light" (red/green/yellow) type info in some of the BW screens like RSMO.

  • Urgent! IDocs in the BW but not in PSA

    Hello Gurus,
    I have a situation where,
    I see the IDocs in the BW inbox with status 53. But the extraction errored out with 90 records receieved but not updtaed. I don't see them either in PSA.
    How do I process this delta.
    Thanks,
    Simmi

    I am still confused.
    1.deleting the request from the data target and scheduling it again from the infopackage is not working. It still complains that the last delta is incorrect.
    2.is it good to turn the status green in the monitor after deleting the request. Am I not sending a wrong signal that I received the last request and scheduling the next one. Won't I loose the records from the previuos requests?

  • IDOC and PSA

    hi all,
    Can anybody tell a case where we can jus use a idoc and cannot use a PSA? are there any cases like this?  is there any real time example where we can use only idoc.?
    Thanks in advance,
    Indudhar

    hi indhudhar,
    welcomw to sdn,
    check out this links:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd
    http://help.sap.com/saphelp_47x200/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/content.htm
    reward points if helpful.

  • Whats the advantage of using  PSA instead of IDOC?

    Hi,
    Whats the advantage of using  PSA instead of IDOC in transfer methods?
    -Arun.M.D

    Hi Arun,
    PSA - Persistent Staging Area
    IDOC - Intermediate Document
    PSA is a temporary storing of all the data.
    IDOC is used as a intermediate document to trnasfer the data from one system to our BW systems.
    From PSA we can transfer 1600 bytes of data & by using PSA we can edit the data also.we can also rectify errors also through PSA,bcoz PSA is a subfunction of our SAP BW system.
    IDOC we can transfer only 1200 bytes of data & we cant rectify the errors if any,bcoz it is not a function of SAP BW.
    Regards,
    Lakshman.G

  • PSA Vs IDOC transfer method

    Hello BW Experts,
    Most of the time i have observed the PSA data transfer method being used.
    1) if the use of psa transfer method is only for the purpose of having the temporary storate, then can we go for the IDOC method if we are not using the temporary storage.
    2) What is the advantage of using IDOC method over PSA when the temporary storage for the load is not required.
    Thanks,
    BWer

    Hi,
    Persistent Staging Area is a transparent database table in which request data is stored in the form of transfer structure.A PSA is created per datasource and source system. It represents an initial store in BW in which the requested data is saved unchanged for source system.PSA
    1) Checks whether extraction from source system is complete
    2)ensures data quality,supports editing,reconstruction and deletion of data.
    IDoc is an Intermediate Document container for exchanging data between R/3,R/2 and non-SAP systems.
    It is a data transfer wherein the data is in the form of packets.
    It is used in the case of flatfiles as debugging is easier.
    IDoc method - The data is packed into IDocs by the source system and sent to BW.
    PSA - In this method the data from the source system is stored in PSA tables before being updated in the Data Target/Info-object.
    The PSA is generally the preferred method because of its various advantages like Reconstruction, Data editing, etc..
    Idocs are generally preferred when the data comes from flatfile. However Idoc transfer method have a limitation - transfer structure must not have more than 1000 Bytes in the character format.
    IDOC is only there because of compatibility reasons. It supports a smaller structure and has no other advantages. You should always use PSA.
    1> DAta sources with the IDOC transfer methode are not supported with ODS object.
    2> you can only create start routine for transfer methode PSA.
    Helplink:
    http://help.sap.com/saphelp_nw04/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/72/31823cdcf5f354e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/de/113037530b7774e10000009b38f839/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/b0/ab8e3cb4340b14e10000000a114084/content.htm
    -Shreya

  • What is difference in PSA and IDOC ?

    Please help me understand what is difference in PSA and IDOC , when and how do we use it. which one is recommended.
    thanks

    Hi,
    If you choose option PSA
    Data is sent directly from the source system to the Business Information Warehouse and is stored in the PSA (Persistent Staging Area)
    From here we can either update the data automatically or manually in
    the corresponding data targets.
    The transfer type here is called the TRF (Transactional Remote
    Function).
    Incase of PSA the length of data record can be upto 1962 where as Idoc it is 1000bytes.
    you have advantage of performance ,large data package and error handling in PSA.
    Data transfer with IDoc
    The data is packed into IDocs by the source system and sent to the
    Business Information Warehouse. In BW your data is saved persistently
    and intransparently in the IDoc store. From there the IDocs can be
    updated in the IDocs manually or automatically.
    It is used for hierarchies load
    Limitations with IDoc is:
    transfer structure must not have more than 1000 Bytes in the character format.
    check out this links:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd
    http://help.sap.com/saphelp_47x200/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/content.htm
    Regards,
    B

  • Idoc status 51 while loading from R/3 to PSA

    hi experts,
    I am loading from R/3 to BW (fiar data), the request is in yellow status and running for long time and showing zero(0) records.
    i have checked that some of the idocs are not posted.
    when i try to push through BD87 still the status is showing 51 only.
    can you plz giv solution for this.
    regards
    venuscm

    Hi,
    Maybe this is due to bugs in the TRFC programs that are solved with the
    attached notes:
    1280898,,IDoc hangs when it is to be sent immediately with
    1338739   RFC calls in the wrong system
    1377863 max no of gateways exceeded
    Also please refer to the following note for additional info:
    1250813 SAPLARFC uses all dialog work processes
    1403974 Determining the maximum connections in transactione error
    I hope it helps you.
    Regards,
    Fran.

  • Data not received in PSA Table(urgent)

    hello,
    While loading Master data full load
    which is a load of 457070 on 2days back
    where only 4lac records r received to PSA but remaining 57070 was missing
    with error<b> Data not received in PSA Table
    </b>
    when the next day we loaded 5lac records and we got the same error<b> Data not received in PSA Table</b> where except 57070 records remaining all reached PSA
    where we tried 2day with 550000 records, same error without 57070 records all other reached to PSA
    I required ur help to solve this
    i will thank by giving points
    Regards
    PSC

    Hi,
    check if there is a TRFC haging in SM58.
    can that be that your DB cannot extend its space for this amount of data.
    How do you perform the load?
    package by package (in series or in parallel)? could that be that the next stage (into IObj) is failing thus stopping the load in the PSA?
    Can you try to perform the same load with only to PSA and then enable the "susbsequent update in target"?
    As already mentionned it could also be that an IDOC is haging...
    please let us know
    Olivier.

Maybe you are looking for

  • How do I authorize the pc to down load music

    I have a nano - and have latest itunes on my pc. Now I want to download purchased muisic to the nano. When I try to do it I get a message telling me I have to authorize the pc to down load the music

  • Doubt with selection screen

    Hi all! I have to show the inspection lot details (QA32) as per the requirements given in the selection screen. In my selection screen , I should have select option for Inspection lot created date(QALS-ENSTEHDAT) and lot created time (QALS-ENTSTEZEIT

  • OS X 6.8 freezes

    My iMac has started to freeze completely randomly.  I am running Snow Leopard.  Sometimes it freezes within a few minutes of restarting, and on other occasions doesn't freeze throughout the working day.  There is no consistency to the task that I am

  • Eclipse+SOA Suite 10.1.3.1 Issues configuring Oracle AS in eclipse

    I have searched all the forums and google but could not find much information. I have installade soa_windows_x86_101310_disk1 and configured SOA Suite 10.1.3.1 whcih works perfectly fine with oracle JDeveloper. Since our developement platform is ecli

  • Schedule Dates changed by APO

    Hi APO people I have a problem in PP whereby the production order schedule dates are immediately overridden by the APO CIF. As a result no scheduling can be done. We are not using PP/DS for scheduling but a third party system. We have also tried usin