Hi All
One of our CRM systems is replaced with SAP CRM.
My question is how can extract or load data by using Datastage.
Please send your inputs.
Thanks
data extract and load SAP CRM
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There are extract and load PACKs for SAP, which you need to purchase from the vendor (IBM or a reseller).
These are certified by SAP AG as generating legal ABAP code.
These are certified by SAP AG as generating legal ABAP code.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
thanks
Ray
Thanks for your inputs. Still i am
I heard SAP Extract and Load packs. These are SAP R/3 ( ABAP ) and BW.
Here my question is the same packs are used for SAP CRM or not.
Here SAP XI also come in to picture. I am not go for that area.
When i discuss with SAP consultants. They are also using BAPI concept (instead of IDOC) when they are working with SAP CRM.
Could you please explain elaborate?
Thanks
SReddy
Thanks for your inputs. Still i am
I heard SAP Extract and Load packs. These are SAP R/3 ( ABAP ) and BW.
Here my question is the same packs are used for SAP CRM or not.
Here SAP XI also come in to picture. I am not go for that area.
When i discuss with SAP consultants. They are also using BAPI concept (instead of IDOC) when they are working with SAP CRM.
Could you please explain elaborate?
Thanks
SReddy
ray.wurlod wrote:There are extract and load PACKs for SAP, which you need to purchase from the vendor (IBM or a reseller).
These are certified by SAP AG as generating legal ABAP code. ...
-
- Charter Member
- Posts: 166
- Joined: Wed Mar 16, 2005 6:52 am
- Location: Mumbai, India
the SAP R/3 pack can do the following:
1. Extract/load data from/to SAP R/3 using IDOC's
2. Extract/load data from/to SAP R/3 using BAPI Calls
3. Given a Logical DB SQL Statement (Built via provided GUI in the stage), generates an ABAP program that extracts data from SAP using CPIC or Write to file.
So long as the same methods are supported on SAP CRM, this "should" also work for CRM; though i have never have seen the R/3 pack used on CRM.
1. Extract/load data from/to SAP R/3 using IDOC's
2. Extract/load data from/to SAP R/3 using BAPI Calls
3. Given a Logical DB SQL Statement (Built via provided GUI in the stage), generates an ABAP program that extracts data from SAP using CPIC or Write to file.
So long as the same methods are supported on SAP CRM, this "should" also work for CRM; though i have never have seen the R/3 pack used on CRM.
Amey Vaidya<i>
I am rarely happier than when spending an entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand.</i>
<i>- Douglas Adams</i>
I am rarely happier than when spending an entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand.</i>
<i>- Douglas Adams</i>
Thanks
Thanks Vaidya
Your inputs are clearer: D
One more question, when we load data in to SAP environment using IDOC, BAPI from our side job is finished with out warnings.
But SAP people are gave a complaint we are not getting exact data what they are expecting at that time how we can do.
Is there any chances go to SAP environment and check the data clarify them.
Could you please explain, if you have a chance please send the screen shots.
Thanks
SReddy
Your inputs are clearer: D
One more question, when we load data in to SAP environment using IDOC, BAPI from our side job is finished with out warnings.
But SAP people are gave a complaint we are not getting exact data what they are expecting at that time how we can do.
Is there any chances go to SAP environment and check the data clarify them.
Could you please explain, if you have a chance please send the screen shots.
Thanks
SReddy
ameyvaidya wrote:the SAP R/3 pack can do the following:
1. Extract/load data from/to SAP R/3 using IDOC's
2. Extract/load data from/to SAP R/3 using BAPI Calls
3. Given a Logical DB SQL Statement (Built via provided GUI in the stage), generates an ABAP program that extracts data from SAP using CPIC or Write to file.
So long as the same methods are supported on SAP CRM, this "should" also work for CRM; though i have never have seen the R/3 pack used on CRM.
-
- Charter Member
- Posts: 166
- Joined: Wed Mar 16, 2005 6:52 am
- Location: Mumbai, India
screenshots would be difficult!!!!
I havent worked with BAPI's a lot though i believe a BAPI returns a status code back to the calling program. This can be written to a file using the BAPI stage. Cant help you much there.
However for IDoc stages,
there are 2 types of issues that may come up :
Issues in building the IDOC staging file and/or in sending it to SAP.
Data Issues that would cause the iIDoc to fail internal SAP validations.
The first set of issues are the only ones trapped and reported by datastage
The second set is something datastage will not know about as this happens exclusively in SAP. You will need to handle this using job logic.
The following general steps are recommended
Steps:
1. Map source values to corresponding valid SAP values by building lookups. This could be provided by your functional consultant.
2. Perform the same validations that SAP will be doing on your IDocs. The validations will ensure that data you write to SAP will always be accepted.
3. Get the formats right. E.G. SAP expects some dates in DDMMYY format and some numbers with the right right number of decimal points
The way to check if IDocs are successfully posted in SAP is to logon to SAP and use the transaction code WE02 (WEDI for a page that lists all IDOc operations)
Status code 53 is success and 51 is usuallyconsidered error however there are many more status codes with descriptions.
I havent worked with BAPI's a lot though i believe a BAPI returns a status code back to the calling program. This can be written to a file using the BAPI stage. Cant help you much there.
However for IDoc stages,
there are 2 types of issues that may come up :
Issues in building the IDOC staging file and/or in sending it to SAP.
Data Issues that would cause the iIDoc to fail internal SAP validations.
The first set of issues are the only ones trapped and reported by datastage
The second set is something datastage will not know about as this happens exclusively in SAP. You will need to handle this using job logic.
The following general steps are recommended
Steps:
1. Map source values to corresponding valid SAP values by building lookups. This could be provided by your functional consultant.
2. Perform the same validations that SAP will be doing on your IDocs. The validations will ensure that data you write to SAP will always be accepted.
3. Get the formats right. E.G. SAP expects some dates in DDMMYY format and some numbers with the right right number of decimal points
The way to check if IDocs are successfully posted in SAP is to logon to SAP and use the transaction code WE02 (WEDI for a page that lists all IDOc operations)
Status code 53 is success and 51 is usuallyconsidered error however there are many more status codes with descriptions.
Amey Vaidya<i>
I am rarely happier than when spending an entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand.</i>
<i>- Douglas Adams</i>
I am rarely happier than when spending an entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand.</i>
<i>- Douglas Adams</i>