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

Similar Messages

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.

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

Errors in IDOC transfer method.....

Hi
I am loading customer data ( LIS , S001) by using transfer method as IDOC. now i got 4 error records. so how do we rectify in IDOC method. i can use PSA also, so that its very easy to rectify errors. But how do we rectify the error records in IDOC method...., any idea gurus......,
Regards
swetha

Looks to me like you're not telling the linker to create a library (DLL). I'm not familiar with Linux, but clearly if the linker if looking for 'main' then its trying to build an executable.

Changing transfer method in transfer rules

I would like to change the transfer method in a TR.
It is set by default to IDoc.
I would like to set it to TRFC with PSA.
However, I can't because it is dimmed.
My aim is to find a workaround to an issue stated in SAP note 120446.
Thxs.
LauQ.

It is a Data Mart source in the same BW system.
I have created an Export DataSource from a PSA.
I cannot activate transfer rules due to a bug (note 120446).
This occurs because the transfer method is IDoc only.
I'm afraid that no solution exist for my problem.
Thxs.
LauQ

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

Transfer method 'TRFC with PSA' is not supported by the source system.

Hi guys
We are getting the following error when we try to open the transfer rules:
Transfer method 'TRFC with PSA' is not supported by the source system.
And when we run the load we are getting this error message:
An RFC call-up triggered the exception
Our source system check is ok. RFC test is ok from both sides.
Please advice what else can be the solution.
Edited by: sam on Nov 6, 2008 4:51 PM

Did you do Right click on Source system and 'Check' option in RSA1-> Source Systems?
Is this problem after upgrade or something like that?
-Abhijit

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

Two Data transfer methods

Hi Gurus
Can any body tell if i will be asked like What are two data transfer methods? Which is the preferred method and why?
thanks in advance
murali

Hi,
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.
refer this help link
http://help.sap.com/saphelp_nw04/helpdata/en/7d/724d3caa70ea6fe10000000a114084/frameset.htm
Regards,
R.Ravi

Transfer Methods, data package

Hi,
I would like to know about
1) the differences between PSA and IDocs
2) the datapackage

Hi,
1.PSA and IDOC methods are two different data transfer methods in BW.
2. PSA will act as backup during dataload failure.
3. Data redundantly stored in the BW system for further usage but not in IDOC methods,
4. IDOC uses two types of IDOC in transferring the data - Information -IDOC and Data IDOC.
5. for dalta loading use PSA is the suggestion.
6. Updation in IDOCmethod is faster.
7. Error occurrence in IDOC is more.
Reg,
Vishwa

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

ABAP Dataflow using FTP data transfer method

Hi,
I am facing this error while executing the ABAP dataflow, the datastore configuration has FTP as data transfer method.
I wanted to know if the ABAP program is generated succesfully and the error is while executing the ABAP program or there is an issue with the generation of ABAP program itself... Please help me understand the issue.
Since I am unable to attach the doc, please see the error message below.
Job name: Job_Module4_ECC_To_BW
(12.2) 02-28-11 11:14:45 (E) (16396:17152) R3C-150607: |Data flow DF_Module4_ECC_To_BW
Execute ABAP program <C:/TEMP/ZECC_To_BW> error < Open File Error --
madap8004\tmp/SAPECC_To_BW_ZCUST_NAME.txt>.
(12.2) 02-28-11 11:14:45 (E) (16772:15444) R3C-150607: |Data flow DF_Module4_ECC_To_BW
Execute ABAP program <C:/TEMP/ZECC_To_BW> error < Open File Error --
madap8004\tmp/SAPECC_To_BW_ZCUST_NAME.txt>.
Regards,
Sri
Edited by: srilakshmi.ponnada on Feb 28, 2011 11:58 AM

Hi,
I am really not clear with your question. This is the first time i am executing the ABAP interface with FTP data transfer method. The madap8004 is the FTP server name. and the path is where the file whould be generated I belive. Is it the problem with any read/write permissions on the server?
-Sri

Right combination needed for transfer method and TTy

Hi,
I have a scenario to map for transfers (affiliated co),
Company code A - apc 1000; nbv 200; accum 800; new value 250;
In company code A
cr apc 1000
dr clrg 250
dr accum 800
cr interco gain 50
In receiving company code B
dr apc 1000
dr asset 50
cr contra 800
cr clg 250
I am unable to do this with transfer method 3, which is new value method. I tried creating new trnsfr variants and TTys but unable to get the above postings.
Please suggest suitable combination of trnsf methods and TTys asap!!!
Thanks
Edited by: rick dermont on May 9, 2008 6:05 PM

Hi,
>Can someone tell me why my post doesn't show up as I typed it? All of the carriage returns were removed so that its one big >paragraph (that is impossible to read).
Because your post is too long.
Because the performance of the java forum software is very bad, the forum admins had to disable the paragraph formatting of "long" messages to keep "acceptable" response times.
This is such a good advertising for Jive software and the j2ee engine...
Olivier

Data Transfer methods

Hi all,
Can anyone please explain me what are synchronous and asychronous data transfer methods?
Where are the settings to be done in R/3 to get data to BI ?
Thanks in advance

Data Transfer
Definition
Synchronous Data Transfer
Data is transferred directly (simultaneously, synchronously) from program to program via CPI-C communication.
Both communications partners must be available at the same time. Because the central SAP system in a typical SAP installation does not run round the clock, but the linked systems are frequently in operation 24 hours a day, asynchronous data transfer is necessary.
Synchronous data transfer has the following disadvantages:
Transfer is not possible is the partner system or the line is not available.
A data backlog in the reciever system causes a data backlog in the sender system. Processing in the application is delayed.
If a connection is broken, it may be necessary to perform a recovery in both systems.
Asynchronous Data Transfer
With asynchronous, or buffered, data transfer, data is temporarily stored in a sequential queue.
Asynchronous transfer has the following advantages:
Wait times in the sender system are avoided.
A recovery is automatically performed in the sender system.
Transfer need not be performed during online time. This avoids placing unnecessary load on the system and thus helps to reduce costs.
The Queue Application Programming Interface (Q-API) is an SAP interface for asynchronous data transfer.
Data is buffered sequentially and processed immediately or later by an asynchronously running process.
One possible processing method is to send data to an external partner system via CPI-C. Data units that belong together can be stored in accordance with transaction and sent to a communications partner.
Data is buffered in queues before it is transferred to the target system.
In an R/3 System, the queues are stored in a relational database. All R/3 database systems are supported.

How to load hierarchie with IDOC as data transfer method

hi ,this is balaji, i have doubt.
can any one please explain, how to up load hierarchies using IDOCs. If any material provided could be helpful.And also give me what are the pros and cons.
regards
balaji.p

HI Balaji,
Check out the following link to load hierarchies:
http://help.sap.com/saphelp_bw33/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm
regards

Transfer Methods...PSA & IDoc

Similar Messages

Maybe you are looking for