Improvements regarding Infopackages and IDOCs during loads
Hi Experts,
I have a questions regarding loading the data into cubes .. what improvements can we make regarding to infopackages and IDOCs.
Any ideas would be appreciated.
thks,
Sunil.
Hi ,
1. Limit the amount of created data packages for each load between 1000 -1500 as described in below mentioned SAP OSS note:
892513 - Consulting: Performance: Loading data, no of pkg, req size
Note: 1000-1500 = sum of data packages over all data targets, i.e. with three targets 350-500 packages
How to limit the amount of data packages for the delta load:
Go to transaction RSA1 select your dedicated infopackage -- menue-- DataS. Default Data transfer --enter the max. nummber of data packages to be created for each delta load.
2. Global level :Use Transaction RSCUSTV6 for changing configuration setting for all the infopackages globally :
(i).Frequency with which status Idocs are sent : It means how many data-IDocs are described by one Info-IDoc.In simple terms after how many data idocs 1 info idocs to be sent .The larger the packet size for a data IDoc, the smaller you should set the frequency. By doing this, you make it possible to get information on the respective data load status in relatively short time periods when uploading data.You should choose a frequency between 5 and 10 but not greater than 20.
(ii)Datapacket size (Number of Data Records per Package) The basic setting should be between 5000 and 20000 depending on how many data records you want to load
.Recommendation :You should not divide up the quantity of data into too large a number of packets since this reduces performance when uploading. The number of data packets should not be more than 100 per loading process.
(III) ROIDOCPRMS : In order to make the RSCUSTV6 settings work you also need to do the related setting in ROIDOCPRMS in source system .
3. Increase the parallelization of the infopackage if possible
Got to transaction SBIW increase the amount of wp which can be used.
Please read also OSS note:
595251 - Performance of data mart: Deactivating tRFC sending in BW
4.. Our Infopackage consists of 3 type of message types RSINFO , RSREQ , RSSEND etc. There is a standard program RSEOUT00 in the source system that is used to pushed IDOCS to OS layer .Therefore create variants for the above message type for this program in the source system .Also create some Background job for this to be run after every 30 minutes .You should not increase the frequency more than this .
Hope this helps .
Regards
Kamal
Edited by: kamal mehta on Dec 25, 2011 1:10 PM
Similar Messages
-
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? ThanksNitesh
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 -
anybody send me quick explanation of ALE configuration and IDOC'S with detailed explanation of each and every step......
i tried a lot but i didn't get that material...........
good material will be rewarded with maximum points..........
plz don't give unnecessary links...........
Message was edited by:
subash chandraHi,
Please check these SAP online help on how to configure both inbound and outbound processing step by step.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/78/217da751ce11d189570000e829fbbd/content.htm
Regards,
Ferry Lianto -
hi
can any one provide me with some scenarios having
idoc and rfc as senders.Hi
To Configure the RFC to FILE scenario ,Proceed as Follows
a. Create an RFC Destination to XI in transaction code (SM59)
b. Create new destination of type T (TCP/IP)
c. Make sure you select Registered Server Program option before writing your program ID
d. Write you program ID (remember it's case-sensitive)
e. In the gateway host and gateway service write the values of your Application system - business system (not the XI server)
Step2:Repository
1) From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2) Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
From the list of Software Component Versions, Choose your own software component version .Click Import.
3) On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
The namespace is ur:rfctofile
4) Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
After this specify the connection parameters to the R/3 system:
4.1) System IS :sapfox
4.2) Client IS :800
Then Save it. The new namespace will be visible under software component version node in the left frame.
Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3) Application server:172.25.5.7
4.4) System number: 00
4.5) User name:developer
4.6) Password: Password of Sap R/3 system.
Then click continue .You will find IDOC and RFC node. Click on this node and select the Idoc or Rfc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the Rfc and Idoc will be available into XI as Message types. So no need to create any Rfc or Idoc Structure. We need to create a structure for file only.
5). Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6) Create new data types.
6.1) Right click on Data types and select New.
Your Data Type is. dt_file
In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
Save the object.
6.2) The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
no need to create Data types. They are imported directly as Message types.
6.3) To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
Select the following.
6.3.1) Category: XSD.
6.3.2) Messages: From All Available Global Elements.
6.3.3) File:
Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7). Create a new Message Type.
7.1) In the left hand frame under Interface objects, right click on the Message types and select new.
7.2) Give a suitable name to the Message type.(MT_ messagetype).
7.3) For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
Save it.
8). Create a Message interface
8.1) In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2). The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
Save it.
9) . Create a graphical mapping between the target document and the sender .
9.1) In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2) As Source message select your own Message type.You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- > Namespace->Imported Objects.
9.3) As Target Message you can choose your Rfc .Choose Search for Integration Object.
9.4) Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5) Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the Source fields to the respective Target Fields.
Save It.
9.6) You can also Test your Mapping by selecting the 'Test Tab'.
9.7) Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10). Create an Interface Mapping.
10.1) In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2) Source interface : Your Outbound Interface (The Source document(Rfc) interface).You can Choose Search for Integration Object.
10.3) Target interface: Your Inbound Interface( The Target document interface).
Then Select 'Read Interface' and Assign your 'Mapping Program' .
Mapping Program: Your Message mapping.
Then Save it.
11.) Finally , in the left hand frame ,go to your change list and Activate it
STEP 3: Directory
1) From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
Create a Scenario Object
2). The First Step is to create a Scenario Object
This will serve as container for all your configuration work. Create and save a scenario object
3) In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4) In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) . Create a Communication Channel.
6). Expand your service and right click on Communication Channel. Name your Communication Channel
Here we need to configure the adapter.
Since the Sender is 'RFC', Specify the following Parameters
For the adapter type , use the F4 help and select RFC.
Specify Sender since the adapter will be sending messages to XI
Specify the following parameters.
Transport Protocol: RFC
Message Protocol: RFC(RFC XML )
Adapter Engine: Integration Server
Adapter status: Active
RFC Server Parameter:
Application Server(Gateway):172.25.5.7
Application Server Service(Gateway Service): sapgw00
Program Id: Id of Registered server program ( it is case sensititve)
And the adapter is configured. Save it
Since the Receiver is File , Specify the following Parameters
6.1 For the adapter type , use the F4 help and select FILE.
6.2 Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3 Specify the following parameters.
Transport Protocol: File Transport Protocol.(FTP)
Message Protocol: File Content Conversion(since the xml files produce by XI need to be converted to text files)
Adapter Engine: Integration Server
For the File system access Parameters, enter the following
Source Directory:Test
File Name: Input.txt
6.4 For the FTP Connection Parameters, Specify the Following
Server:172.25.5.240
Port: 21(by default)
Data Connection: Passive
Connection security: None
Connection Mode: Permanently
Transfer Mode: Binary
6.5 For Processing Parameters, Specify the following
File construction mode: Add Time Stamp
File Type: Binary
6.6 For Content Conversion Parameters, Specify the Following
RecordSet Structure:
Adapter Status: Active
The receiver file adapter is now configured. Save your Communication Channel.
Create an Receiver Determination.
7). From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1) Select your sender service and interface.
Sender:
Party: blank
Service: Sender service(Business system)
Interface : Sender interface
7.2) In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
Create an Interface Determination.
7.3) Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1) In the Receiver Determination you just created, have a look at the area Configuration Overview for Receiver Determination at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2) In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3) You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4) A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5) When you are done , Save the Interface determination object.
8.) Create a Sender Agreement.
In the left hand frame , right click on Sender Agreement ->New
8.1) Specify the following:
Party: blank
Service: Select your own Business system
Interface: Outbound Interface
8.2) In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.) Create a Receiver Agreement.
Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1) Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2) In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
Specify the following:
Party: blank
Service: Select your own Business system
Interface: Inbound Interface
9.3) In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
Your Configuration is complete. Activate the objects.
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Step2:Repository
1) From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2) Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
From the list of Software Component Versions, Choose your own software component version .Click Import.
3) On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
Your NameSpace is urn:idoctofile
4) Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
After this specify the connection parameters to the R/3 system:
4.1) System :sapfox
4.2) Client :800
Then Save it. The new namespace will be visible under software component version node in the left frame.
Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3) Application server:172.25.5.7
4.4) System number:00
4.5) User name: developer
4.6) Password: Password of Sap R/3 system.
Then click continue .You will find IDOC node. Click on this node and select the Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5). Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6) Create new data types.
6.1) Right click on Data types and select New.
Your Data Type is :dt_file
In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
Save the object.
6.2) The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
no need to create Data types. They are imported directly as Message types.
6.3) To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
Select the following.
6.3.1) Category: XSD.
6.3.2) Messages: From All Available Global Elements.
6.3.3) File:
Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7). Create a new Message Type.
7.1) In the left hand frame under Interface objects, right click on the Message types and select new.
7.2) Give a suitable name to the Message type.(MT_ messagetype).
7.3) For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
Save it.
8). Create a Message interface
8.1) In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2). The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
Save it.
9) . Create a graphical mapping between the target document and the sender .
9.1) In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2) As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- > Namespace->Imported Objects.
9.3) As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4) Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5) Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the Source fields to the respective Target Fields.
Save It.
9.6) You can also Test your Mapping by selecting the 'Test Tab'.
9.7) Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10). Create an Interface Mapping.
10.1) In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2) Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3) Target interface: Your Inbound Interface( The Target document interface).
Then Select 'Read Interface' and Assign your 'Mapping Program' .
Mapping Program: Your Message mapping.
Then Save it.
11.) Finally , in the left hand frame ,go to your change list and Activate it
STEP 3: Directory
1) From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
Create a Scenario Object
2). The First Step is to create a Scenario Object
This will serve as container for all your configuration work. Create and save a scenario object
3) In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4) In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) . Create a Communication Channel.
6). Expand your service and right click on Communication Channel. Name your Communication Channel
Here we need to configure the adapter.
Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
For the Receiver, Specify the following Parameters
6.1 For the adapter type , use the F4 help and select FILE.
6.2 Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3 Specify the following parameters.
Transport Protocol: File Transport Protocol.(FTP)
Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
Adapter Engine: Integration Server
For the File system access Parameters, enter the following
Source Directory:Test
File Name: Input.txt
6.4 For the FTP Connection Parameters, Specify the Following
Server: 172.25.5.240
Port: 21(by default)
Data Connection: Passive
Connection security: None
Connection Mode: Permanently
Transfer Mode: Binary
6.5 For Processing Parameters, Specify the following
File construction mode: Add Time Stamp
File Type: Binary
6.6 For Content Conversion Parameters, Specify the Following
RecordSet Structure:
Adapter Status: Active
The receiver file adapter is now configured. Save your Communication Channel.
Create an Receiver Determination.
7). From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1) Select your sender service and interface.
Sender:
Party: blank
Service: Sender service(Business system)
Interface : Sender interface
7.2) In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
Create an Interface Determination.
7.3) Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1) In the Receiver Determination you just created, have a look at the area Configuration Overview for Receiver Determination at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2) In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3) You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4) A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5) When you are done , Save the Interface determination object.
8.) Create a Sender Agreement.
In the left hand frame , right click on Sender Agreement ->New
8.1) Specify the following:
Party: blank
Service: Select your own Business system
Interface: Outbound Interface
8.2) In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.) Create a Receiver Agreement.
Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1) Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2) In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
Specify the following:
Party: blank
Service: Select your own Business system
Interface: Inbound Interface
9.3) In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
Your Configuration is complete. Activate the objects.
plz rewards points
vikas -
Iam an Infant as far as ABAP is concerned. I have some basic ABAP knowlegde and i know SAP scripts and smart forms. But no idea about data transfer techniques. I have one silly question :
Is it possible to learn ALE and IDOC on a home PC. I mean can i practice them at home. I dont have any network access so i wanted to know can i practice at home on my personal system.
Can my home PC behave as both sender and receiver system. If it is possible pls let me know how to go about it guys.
I know this is a very very silly question, but as i said, iam still learning to crawl in ABAP. It will take some time before i walk.
Thank You.Hi guys,
I must thank every one of you for sending such quick and helpful responses. I bought the book "ALE, EDI and IDOC" from Aravind Nagpal and its a great book for beginner as well as for an expert. I have started practising ALE my PC by logging into 2 clients and it is working fine. I was able to send and receive the IDOC.
Thank you again.
This is a great forum,
Cheers,
Mahesh.
Edited by: Mahesh Kumar on Jan 21, 2009 3:32 PM -
Regarding smartforms and idocs
what is the ASN in ABAP?is this any file format?
Can't we use an ALE IDOC technique with two different versions of SAP systems?what is the ASN in ABAP?is this any file format?
Can't we use an ALE IDOC technique with two different versions of SAP systems? -
What are the settings for datasource and infopackage for flat file loading
hI
Im trying to load the data from flat file to DSO . can anyone tel me what are the settings for datasource and infopackage for flat file loading .
pls let me know
regards
kumarLoading of transaction data in BI 7.0:step by step guide on how to load data from a flatfile into the BI 7 system
Uploading of Transaction data
Log on to your SAP
Transaction code RSA1LEAD YOU TO MODELLING
1. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
2. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( Transaction data )
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
In left panel select info provider
Select created info area and right click to create ODS( Data store object ) or Cube.
Specify name fro the ODS or cube and click create
From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
Click Activate.
Right click on ODS or Cube and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets.
4. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used.
Loading of master data in BI 7.0:
For Uploading of master data in BI 7.0
Log on to your SAP
Transaction code RSA1LEAD YOU TO MODELLING
1. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
2. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( master data attributes, text, hierarchies)
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
In left panel select info provider
Select created info area and right click to select Insert Characteristics as info provider
Select required info object ( Ex : Employee ID)
Under that info object select attributes
Right click on attributes and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets. -
Regarding output type and idoc trigger issue
Hi
i need to copy pgi quantity into sales order quantity for that i write a code into user exit MV50AFZ1. code is working fine but
output type and idoc is not trigger due to this. In this exit to update sales order quantity i used bapi *BAPI_SALESORDER_CHANGE . can anyone tell me why o/p type and idoc not trigger ,what is the reason and what is the solution for this?
Thanks
DineshHi Dinesh,
Did you activate the enhancement for user exit ?
Did you check if the output type is configured correctly ?
Put a debugging point and see if control is coming there.
Regards,
Nisha Vengal. -
Regarding the Message Type and IDOCS related to IS-Banking
Hi Gurus,
can any one provide me the Message Type and IDOCs related to IS-Banking.
Regards.
Kiran kumar.Hi,
Refer this link,
http://www.stylusstudio.com/edifact/d04b/BANSTA.htm
Hope it helps you. -
Regarding Transformation and Data Transfer Process(DTP)
Dear Gurus
1) Transformation replaces the transfer rule and update rule.
2) DTP replaces the info package.
Hencse, there is a some advantages are there in Transformation and DTP.
I couldn't understand in help.sap.com.
Could you please tell me in simple language what all are the new features are there in Transformation and DTP which is not possible in Transfer rule, Update rule and infopackage.
Thanks and Regards
RajaHi Raja,
These are the advantages of DTP and Transformation over their predecessors.
DTP:1)Improved transparency of staging processes across data warehouselayers (PSA, DWH layer, ODS layer, Architected Data Marts)
2)Improved performance:Intrinsic parallelism
3)Separation of delta mechanism for different data targets: delta capability is controlled by the DTP
4)Enhanced filtering in data flow
5)Repair modes based on temporary buffers (buffers keep complete set of data)
Transformation: SAP NetWeaver2004s significantly improves transformation capabilities. The improved graphical UI contributes to decrease TCO.
1)Transformation Improved performance, flexibility and usability
2)Graphical UI
3)Unification and simplification of transfer and update rules
4)New rule type: end routine
5)New rule type: expert routine (pure coding of transformation)
6)Unit Conversion Capabilities for unit conversion during data load (and reporting)
Assign points if it is helpful.
Cheers,
Bharath -
P67a-GD65 System Freezes and Recovers During 3D gaming and Online Video
The Problem:
Temporary system freeze with audio stutter. The system recovers 30sec - 2min later.
Key presses made during freeze will execute after system recovers (ctrl+alt+delete for example)
Usually, but not always, I see an error message in the system tray and I do NOT experience bsod.
This happens seemingly at random from 3D accelerated applications, and web browsing. Games such as BF3 (moderate), WoW (seldom), Planetside 2 (frequently), Minecraft (seldom), Hawken (seldom), etc.
Also happens frequently in both Internet Explorer 9/10, Firefox, Chrome, and Steam store browser. Typically when watching steaming video (youtube, HULU, flow player, etc)
but Pandora audio streaming also seems to create the conditions where this happens.
Error Message:
"Display driver stopped responding and has recovered
Display driver NVIDIA Windows Kernal Mode Driver 314.07 stopped
responding and has successfully recovered"
The problem also shows up in the Windows reliability history with the following data:
Source
Windows
Summary
Video hardware error
Date
3/6/2013 9:11 PM
Status
Not reported
Description
A problem with your video hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Files that help describe the problem
WD-20130306-2010.dmp
sysdata.xml
WERInternalMetadata.xml
Extra information about the problem
BCCode: 117
BCP1: FFFFFA8011E0C4E0
BCP2: FFFFF8800654A198
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
My System Hardware:
CPU: Intel i7 2600k @ 4.5ghz
Motherboard: MSI p67a-gd65 (B3 stepping)
Memory: G.SKILL Sniper 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600
GPU: Originally MSI 6950 2GB. Replaced with EVGA 670 FTW 2GB.
PSU: CORSAIR HX Series HX850 850W
HDD: 3x Western Digital WD RE4 WD5003ABYX 500GB in Raid 0
OS: Windows 7 Home Premium SP1 with all updates
Case/Cooling: Silverstone Raven 2E with Thermalright silver arrow cpu heatsink
What I've tried:
Updated all motherboard drivers and bios (4.3) to current versions (no improvement)
Updated display drivers (in safe mode with driver sweeper. No improvement)
Updated Realtek Audio drivers for onboard sound (no improvement)
Updated Intel Rapid Storage drivers (no improvment)
Cleared CMOS and tested system at default settings with no overlock (no improvement)
Flashed 6950 back to 6950 stock bios and removed overclock (no improvement)
Replaced old 6950 with new GTX 670 (problem still occurs in the same exact way)
Tried GPU in 2nd PCIe slot. No improvement.
Checked GPU Temps. GTX 670 fan profile in EVGA Precision X set to keep temp below 70 degrees Celcius. Card maxes at 60 degrees under heavy gaming load.
Complete reformat of raid array with fresh install of Windows (4 different times) Seemed to help for a few days, then freezes came back
Ran OCCT and Prime 95 Torture tests separately for a few hours at stock and OC settings. System stable with core temps of high 50's overclocked, and low 40's stock.
Ran Memtest86 for 10 hours with zero errors.
Used digital multimeter to test 12v rail on PSU. Noted solid 12v reported. Didn't test other rails.
Unplugged PSU cables from motherboard and reattached firmly
Ran HD Tune and Data Life Guard Tools for error checking on hard disks. Zero errors found.
Disabled Windows Aero (no improvement)
Updated Adobe Flash Player to latest setting (no improvement)
Removed Adobe Flash Player (no improvement)
Turned off Adobe Flash hardware acceleration (no improvement)
*EDIT: Forgot that I also adjusted Nvidia driver profiles for apps that have frozen to include power preference to max performance
All of my hardware with the exception of the new 670 was purchased and configured back in February of 2011. This problem first occured in BF3 multiplayer sometime in early 2012,
and has gradually been happening more frequently. Web searches found many individuals with this error, but the solutions are all over the map, and I've tried just about everything that I've found.
I think I've narrowed the problem down to the motherboard, but I just can't find a clear answer or solution. Maybe it's the raid array? I really thought replacing the GPU would solve my trouble here
and I was...NOT happy when it happened again with the new 670 that I scored for $250 after amazon gift cards. I typically get kicked/disconnected during online game play when this happens and I'm ready to be done with it. I was hoping to fix the issue without needing to buy new hardware, but I don't see any other way at this point.
My patience runs thin. Please help!Quote from: Froggy Gremlin on 11-March-13, 15:28:36
Might want to ask for the special archive to return the mainboard to pre-Ivy support UEFI/BIOS and then test again with everything set to auto/stock/default.
Already tested that before updating to 4.3. I started having the problem on 1.8, then 1.J0, then 4.3.
Quote from: Bernhard on 11-March-13, 15:30:29
Just a shot in the dark.
The length of time that your CPU has been running at the OC could have accelerated the eventual degradation.
Have you tested your CPU in another board or do you have access to a "known good" CPU to test in your system ?
I do not have another 1155 lga board to test the cpu in unfortunately, hence the CPU stress testing. Based upon previous experiences with multiple overclocked systems that I've run at much more aggressive overclocks, I don't believe I'm seeing a processor failure, though I can't rule out the possibility.
Quote from: xmad on 11-March-13, 23:26:01
Quite a few components can cause this.
Do you have a friend that could lend you a psu to test? A weak of failing PSU can often be the cause of something like this?
No I don't have another PSU to test. I did use a digital multimeter to test the 12v rail, as well as the motherboard contacts for testing voltage to the cpu and system They were all right in line with what I'm seeing reported in the bios. I did not test these contacts while the system was under load however, so I may need to do it again. -
PI 7.1 scenario -- File to File , File to IDOC and IDoc to File Scenario
Hi All,
*I have PI 7.0 . I have in that File to File , File to IDOC and IDoc to File Scenarios*
File to File -- This scenario is working fine.
File to IDOC -- Setting done in PI 7.0 like SM59, IDXI, IDX2 and in R/3 like SALE (logical system)--- This scenario is working fine.
IDoc to File -- Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
Now I need to move to PI 7.1 -- for File to File , File to IDOC and IDoc to File Scenarios.
Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
Regards>
Rickkk wrote:
> Hi,
>
> Idoc metadeta is updated through idx2?
>
> Regards
If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of. -
Loading through Process Chains 2 Delta Loads and 1 Full Load (ODS to Cube).
Dear All,
I am loading through Process chains with 2 Delta Loads and 1 Full load from ODS to Cube in 3.5. Am in the development process.
My loading process is:
Start - 2 Delta Loads - 1 Full Load - ODS Activation - Delete Index - Further Update - Delete overlapping requests from infocube - Creating Index.
My question is:
When am loading for the first am getting some data and for the next load i should get as Zero as there is no data for the next load but am getting same no of records for the next load. May be it is taking data from full upload, i guess. Please, guide me.
Krishna.Hi,
The reason you are getting the same no. of records is as you said (Full load), after running the delta you got all the changed records but after those two delta's again you have a full load step which will pick whole of the data all over again.
The reason you are getting same no. of records is:
1> You are running the chain for the first time.
2> You ran this delta ip's for the first time, as such while initializing these deltas you might have choosen "Initialization without data transfer", as such now when you ran these deltas for the first time they picked whole of the data.Running a full load after that will also pick the same no. of records too.
If the two delats you are talking are one after another then is say u got the data because of some changes, since you are loading for a single ods to a cube both your delta and full will pick same "For the first time " during data marting, for they have the same data source(ODS).
Hope fully this will serve your purpose and will be expedite.
Thax & Regards
Vaibhave Sharma
Edited by: Vaibhave Sharma on Sep 3, 2008 10:28 PM -
while in email today, the computer began flashing. I had to turn off with button. When I turned it back on, I got the apple icon and the moving loading wheel. It would turn for about 60 seconds and then stop. I turned off again. I now have a black screen.
Hi wiesenruth,
If you are having issues starting up or booting your computer, you may find the following articles helpful:
Troubleshooting: My computer won't turn on
http://support.apple.com/kb/TS1367
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/ts2570
Regards,
- Brenden -
Examples needed for Idoc to file and IDOC to web services
Hi ,
Could any one of you give some examples which take me through step-by-step in building IDOC-TO-FILE and IDOC-TO-WEB SERVICES?
Regards,
XI Developer.Hi,
For IDOC scenario you need to first do the required configuration:
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Testing purpose u can use the below method:
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters --> For Idoc sender: IDOC -file
IDOC configuration:
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
SOAP scenario:
YOu have to first create the WSDL through ID and import that WSDL in to IR external definition.
Refer the below thread and pdf:
How to use SOAP adapter:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
SAP AII - How to consume and expose webservices ?
Thnx
Chirag
reward points if it helps.
Maybe you are looking for
-
Display Undetected: Cintiq 12WX to iMac via DVI + Mini Displayport Adapter Thunderbolt
Hello all. I'm connecting my Wacom Cintiq 12WX to an iMac 27-inch, Late 2013 (brand new) via a DVI cable connected to the iMac's thunderbolt port with a Mini DisplayPort to DVI adapter. Returning a "No Sync" response on the tablet, iMac is not detect
-
Backstory: There are two possible events that could be causing this 1: At some point I may have followed a ''Tinyurl' link that consquently lead me to a youtube video, to which youtube worked perfectly fine before hand, and this is where i witnessed
-
Show Reminders in iCal not showing
I've just discovered Reminders - and I love it! But I can't get it to show up in iCal, either on my Macbook Air or in iCloud on the web. In the view menu, I don't see the Show Reminders option. Help!
-
Oracle.jbo.PersistenceException: JBO-26035 while inserting a new row.
Getting the following exception. oracle.jbo.PersistenceException: JBO-26035: Secondary entity usage DocumentTypeMappings is missing parts of association description. at oracle.jbo.server.ViewDefImpl.processEntityAssociations(ViewDefImpl.java:793
-
Pricing problem in sales order creation
Hi friends, My requirement is to create sales order with ref to contract i am using 'BAPI_SALESORDER_CREATEFROMDAT2' , and I am extracting data from konv table to get price through condition record , but i am getting 4 messages (S) SALES