Inital load on standalone CRM

Hi all,
I have to upload arround 1 million record in CRM system. and i am using LSMW Idoc method....in which i am using CRM_XIF_PARTNER_SAVE and CRM_XIF_PARTNER_SAVE_M IDoc. And i have create the file port and the partner number.
But i am stuck at this point .. Any one who has done this before can sedn me step doc which help me in doing so...
Points will be rewarded....
Thanks in advance
Vertika

Hi Vertika,
This are the steps I have done in order to load business partners in SAP CRM. I use a flat file as data source, LSMW as SAP CRM tool, IDOC as import method and message type CRMXIF_PARTNER_SAVE_M
1. Customizing for Business Partners. Transaction SPRO. You have to check if all the customizing for BP is defined (Roles, Number Ranges, Groupings, etc).
2. Create Ports for LSMW - Transaction WE21
3. Create Partner Nº for LSMW - Transaction WE20. In this step you must set US for partner and include CRMXIF_PARTNER_SAVE_M as Inbound Parameter.
4. Create a Project in LSMW. Transaction LSMW.
5. Create a SubProject in LSMW. Transaction LSMW.
6. Create a Object in LSMW. Transaction LSMW.
7. Set IDoc Inbound Processing in LSMW. Transaction LSMW. In this step you must set the port, the partner type an number and activate the idoc inbound processing.
8. Automatic Workflow Customizing. Transaction SWU3. You must execute the automatic Workflow Customizing.
9. Verify Workflow. Transaction SWU3. You must start the Verification Workflow.
10. Maintain Object Attributes. Transaction LSMW. In this step you must specify the import method (IDOC), the message type CRMXIF_PARTNER_SAVE_M and the basic type CRMXIF_PARTNER_SAVE_M02
11. Maintain Source Structures. Transaction LSMW. In this step you define a name for your source structure.
12. Maintain Source Fields. Transaction LSMW. In this step you define the name, length and type for all the fields that you are going to include in the flat file where you have stored the source data.
13. Maintain Structure Relations. Transaction LSMW. In this step you define the segments of the IDOC that you want to map.
14. Maintain Field Mapping and Conversion Rules. Transaction LSMW. In this step you define the mapping and conversion rules between the source fields and the segments included in the IDOC.
15. Specify Files. Transaction LSMW. In this step you define the source files (from your PC or the CRM server). You must define wich are the separator in the flat file (tabulator, comma, etc).
16. Assign Files. Transaction LSMW.
17. Read Data. Transaction LSMW. In this step the CRM system read data from flat file.
18. Display Read Data. Transaction LSMW. You have to check if the data from the flat file have been read in a correct way.
19. Convert Data. Transaction LSMW. In this step, the CRM system map and convert the data.
20. Display Converted Data. Transaction LSMW. You have to check if the data have been mapped and converted in a correct way.
21. Start IDoc Generation. Transactio LSMW. In this step, the CRM system create the IDOC. The IDOCs created remains with status 64.
22. Start IDoc Processing. Transactio LSMW. In this step, the CRM system process the IDOC. The IDOCs processed change the status to 51 (incorrect) or 53 (correct).
23. Check the IDOCs. Transaction WE02.
24. Check the bdocs. Transaction SMW01. Every IDOC processed OK, generate a BDOC BUPA_MAIN. You have to check is the bdoc status is green.
25. Check the Busines Partner. Transactio BP. You have to check if the Business Partner are created and the data are ok.
Best Regards,
Alvaro

Similar Messages

Initial Load on standalone CRM

What are the different ways of loading initial master data on standalone CRM ?
I know we can do a manual set up of Org Model but can we do it by any other means like CATT or connect with R/3 for a while and then perform the initial load etc
Many Thanks !!

Hi Anand,
I would also like to know how to make an initial load (Business Partner and products) for a CRM standalone solution. Could you please describe in detail how to do this with IDocs?
Thanks,
Cristina
PS: I did not open the thread, but if it helps, we will find a way to allot the points.

CRM Init load failure Errors In Source System 340

Hello
This is my first question on SDN.........could anyone help me please????
When I am attempting to do an Init load to ODS 0CRM_PROH and to MD Infoprovider 0CRM_SRVGUI, using Infosource 0CRM_SERVICE_PROCESS_H the load is failing and I get the message Errors In Source System 340.
Version is BW3.5 and CRM4.0
Thanks
Emma

Thanks Venkat
I have considered this but could you please explain the following:
If I start a full load at say 10am. It finishes at 11am. If I then do an init no data at 11.05am after the full load has finished. then I do a delta. Does this mean that my delta will pick up data only from when the init no data was done and set the timestamp?
So I will lose any data between 10am (when I started full load) and 11.05am (when I ran init no data)?
Emma

Init load very long runtime 0CRM_COMPLAINTS SALES Analyses

Hi,
We have launched a init load (infopackage 0CRM_COMPLAINTS)(BI 7.0) which extract 180201 claims from our CRM 2007 system.
The first packet (data package size 5000 records) have been extracted in 5minutes, but when it begins the 10 packets, it last 20min and 30 between each of them.
This treatment lasted 12 hours (we don't see optimization point at the moment)
The first thought is to decrease packet size but I don't find specific note about this problem, or any lead.
Any help will be grateful.
Chris

HI
you check the SAP Note 692195 - Question 1 ( shown below )
Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues)
Suggestion 1: Please implement notes 653645 (Collective note) and 639072(Parallel Processing).
The performance could be slow because of the wrong control parameters used for packaging.
You can change the package size for the data extraction.
Also note that changing the package size in the transaction SBIW would imply a change for all the extractors. Instead, you could follow the path in the bw system.
Infopackage (scheduler) > Menu 'Scheduler' > 'DataS. default data transfer' > maintain the value as 1500 or 1000(This value is variable)
The package size depends on the Resources available at the customer side (The no of parallel processes that could be assigned = 1.5 times the no of CPU's available approx.)
Regards,
Sathya

Multiple free goods for one item in standalone CRM

Hi Gurus,
We are trying to implement multiple free goods for one item in standalone CRM.
As per SAP.help.com, it says that we can configure multiple free goods scenario in standalone CRM system.
We tried to set up this in our system. Basically we want to implement the scenario, where a user wants to purchase item A, he should get a prompt for choosing between two free goods B and C.
We did the relevant IMG settings required for Free goods at IMG ->CRM -> Basic Functions -> Free Goods.-> Set up Free Goods
We also did the relevant item category determination where we have made an entry with
Item Usage = " Free Goods" , Main item cat. = "TAN' , Item Category = "TANN".
Now we went to create condition records in the path "SAP Menu -> Master Data -> Prices and Conditions -> SAPCND/GCM - Maintain condition"
We chose Application ="PRT", MaintenanceGrp="PRT_FGOODS", Maintenance context ="GCM"
Then while creating conditon records , when I try to create two condition records where the Main Product is same but free good product is different, the system is not allowing to save these two condition records.
it is giving error "Overlapping validity periods for two condition records".
Please advice, if i am missing something. Thanks in advance for your help.
thanks,
Randhir
Edited by: Randhir Soni on Feb 8, 2010 8:12 AM

Constraints in free goods in R3 taken from SAP library
Free goods can only be supported on a 1:1 ratio. This means that an order item can lead to a free goods item. Agreements in the following form are not supported: u2018With material 1, material 2 and material 3 are free of chargeu2018 or u2018If material 1 and material 2 are ordered at the same time, then material 3 is free of chargeu2018.
Free goods are not supported in combinations with material structures (for example, product selection, BOM, variants with BOM explosion).
Free goods are only supported for sales orders with document category C (for example, not quotations).
Free goods are not supported for deliveries without reference to a sales order.
Free goods cannot be used in make-to-order production, third-party order processing and scheduling agreements.
If you defined a free goods for variants in a generic article (only SAP Retail), you can only process the variants in the purchase order and goods receipt individually (as single articles). In other words, you cannot process them using the generic article matrix.
This answers your qn Not possible in R3
If you are on Retail scenario this is possible thro bonus buy schemes
But a lot of customizations needs to be done and you need a retail server to do that
Regards
Raja

FI_AR_4 Infosource(standard) Init Load

Hi Gurus,
I have an issue regarding INIT load for FI_AR_4 Infosource.It shows yellow status though R/3 has data.I got the records into BW using full upload.
To enable DELTA upload, I Intialised the DELTA "<b>without data transfer</b>".It gives me an error that I cannot Initialise once again after FULL upload.
Could you please help me to solve this.
Regards,
Venkat

That is true with the GL if you are using the GL. Once the GL is initialized, AR and AP have to follow that, if GL is not being used, don't worry about it.
Check you ODS status (change -> ODS...). Look at the settings and make sure the "update status automatically" is set, otherwise the system waits for you to turn it green manually.
/smw

INIT load to the 0FIAR_C03

Hi
I am uploading data to the cube 0FIAR_C03, I am using the standard infosource, I have uploaded data using INIT load it replies that INIT update is not possible to the cube 0FIAR_C03 but the full load is possible.
What can I do to make it delta and INIT enabled ?

Hi Sun,
your datasource have to be replaced (from BW PlugIn 2001.1) by the new extractor 0FI_AP_4, that allows delta management !
Look at OSS Note 401646 'New DataSources for Line Items from FI-GL, FI-AP..."
Hope it helps!
Bye,
Roberto

Init Load showing in yellow state.

Hi all,
I am trying to do init for SRM data source to ODS object.
The init load is showing yellow state (0-0 records).
There is no data available in SRM related to this data source.
Can anyone please tell me why it is in yellow state instead of green.
Thanks
S VR.

Hi S VR,
In the monitor screen go to the Status Tab > click on the lights next to Total > Make it Red and save > the system will prompt a couple of messages, say Yes to them. Then you can Manual Update. Once all packages are done (green), then again Status tab > click onthe lights next to Total > Delete Statsu; back to request status > Save. The request should now be green.
else
try repair full request option it can help you..
Hope this helps...
Assign points if helpful...
Regards,
NR
Edited by: N R Pradeep Reddy on Apr 14, 2008 6:14 AM

No selection in infopackage possible when Init-load

Hello all,
I have created a loading proccess from an ODS to an Infocube via delta-load. I want to restrict the data and therefore I want to use the selction tab from the infopackage menu. But this is just possible when I choose full-load. When I choose Init-load or delta-load, there is no restriction possible in the selection screen.
Ho can I restict data when i load via delta? the release is 3.5.
Any help would be great.
Best Regards,
Stefan from Munich/Germany

Dear Stefan,
You can not restrict an init/ delta load from an DSO, because the data loaded will correspond to the change log table of the DSO.
What you can do is a "fake" delta. You put a "changed date" in you DSO (filled by the sy-datum in the update rule) and then do a full load from your DSO to your cube with the selection you want and changed data = today. But you will have to be careful in case of reload...
Hope it helps,
Rodolphe

How to see the init load in bi 7.0

hello frnds,
In bi 7.0 when v load data it show the full load and delta load option only,,so my question is, if delta load r there then definately init load also avilable,so where is that init load,,plz guys tell me where is that option,,
2nd question is about compression in bi 3.5,,after loading data into infocube when i do compression it ll not work,,why i dont know ,,plz help me
Thanks
Rosy

Hi Rosy,
Init with data load is Full upload + Delta Enables. Once you run this it will fetch entire records from the Source, delta will be automatically enabled and next time onwards only delta will be coming to BW.
Before you can request a delta update, you must first initialize the delta process.Delta initialization can only be simulated for DataSources from SAP source systems if the DataSource supports this.
I hope the below link will be helpful,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0db2280-8242-2e10-b6a5-86a46d0feb25?QuickLink=index&overridelayout=true
Regarding compression, please check the below link,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c035d300-b477-2d10-0c92-f858f7f1b575?QuickLink=index&overridelayout=true
Thanks,
Vinod

Lis datasources , INIT loads,

Hi,
i am working on BI7, and v are using some lis datasources like 2lis_02_s013 and
2lis_02_s017 , I want to do init load with data transfer option and after that create delta loads to be used in process chains, i am geeting errors saying that datasources is till updating in sources system for init load
please guide me in this regard,
plz send ur answers to [email protected]
or
[email protected]
correct answers will be awarded points

Hi,
You can use the infopackage to create the init load on the datasource and transfer the data to PSA and from there you can transfer the data into data targets using DTPs either you can go with full update or you can load the deltas from here again.
Creating init loads, and then deltas is all done in the datasource tree where you create the infopackage to extract the data from the source system to BW system.
REgards.

Whats the Actual use of the Setup table apart from the Full/Init loads

Hi guru's
could u explain whats the Actual use of the Setup table apart from the Full/Init loads in Lo Extraction

Hello Guru,
The Setup table is used mainly for storing the Historical data whereas the new and changed records will be maintained in the Update table.
By storing the Historical data in the setup table you don't need to disturb the Application table anymore.
Please go through the following blogs
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/vikash.agrawal/blog/2006/12/18/one-stop-shop-for-all-your-lo-cockpit-needs
https://websmp201.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002719062002E
Hope it helps
Thanks,
Chandran

SRM to BW - init load

Hello Everyone,
i need to do a init load for datasource 0BBP_TD_PO_1. I know the function of init load, but i want to know the process for the initaliasation of the SRM init load. Do i need quiet time, how to perform init load like flushing the queue etc. I dont how the process of initialition of SRM data. Please provide the steps to perform initalisation process.
Thanks in advance,
Lasya.

Hi Lasya,
SRM Init load is no different. Please donot get confused with LO cockpit.
I would definately prefer to do the init load at a quite time... I dont think I need a downtime though.
Steps to do this:
Check in RSA7.. if you have any entries.
Open the info package...(Init Info pak)...and simply cilck on the start button.
I dont think you need to look into LBWQ1 and use the programs to manually run the V3 updates.
Assign points if helpful
Thanks
kalyan

Tab-highlighting duirng the inital Load of the application

Hi All,
Currently I m developing a Flex application where in the
home page,set of seven tabs are there as per the design.
Whenever i click the tab, I have changed the style of the
text to bold..to make it look like highlited.But this works fine
except the inital load of the first page..In the main appliation
tag,i have used the initialize and also the creationComplete events
to make that tab--higlited.Can anyone suggest me a solution to
solve this issue?
I tried using the following code..to highlite..but not
working for the first time..initial display
myTabBar.selectedIndex=4;
myViewStack.selectedIndex=3;

Look at the following thread: [http://www.webmasterworld.com/javascript/3396582.htm] It will involve modifications to your mod pl/sql install..
Thank you,
Tony Miller
Webster, TX

Difference: Full load, Delta Load & INIT load in BW

Hi Experts,
I am new to SAP BW Data warehousing.
What is the difference between Full load, Delta Load & INIT load in BW.
Regards
Praveen

Hi Pravin,
Hope the below helps you...
Full update:
A full update requests all the data that corresponds with the selection criteria you have determined in the scheduler.
You can indicate that a request with full update mode is a full repair request using the scheduler menu. This request can be posted to every data target, even if the data target already contains data from an initialization run or delta for this DataSource/source system combination, and has overlapping selection conditions.
If you use the full repair request to reload the data into the DataStore object after you have selectively deleted data from the DataStore object, note that this can lead to inconsistencies in the data target. If the selections for the repair request do not correspond with the selections you made when selectively deleting data from the DataStore object, posting this request can lead to duplicated data records in the data target.
Initialization of the delta process
Initializing the delta process is a precondition for requesting the delta.
More than one initialization selection is possible for different, non-overlapping selection conditions to initialize the delta process when scheduling InfoPackages for data from an SAP system. This gives you the option of loading the data
relevant for the delta process to the Business Information Warehouse in steps.
For example, you could load the data for cost center 1000 to BI in one step and the data for cost center 2000 in another.
The delta requested after several initializations contains the upper amount of all the successful init selections as the selection criterion. After this, the selection condition for the delta can no longer be changed. In the example, data for cost
centers 1000 and 2000 were loaded to BI during a delta.
Delta update
A delta update requests only the data that has appeared since the last delta. Before you can request a delta update you first have to initialize the delta process. A delta update is only possible for loading from SAP source systems. If a delta update fails (status red in the monitor), or the overall status of the delta request was set to red manually, the next data request is carried out in repeat mode. With a repeat request, the data that was loaded incorrectly or incompletely in the failed delta request is extracted along with the data that has accrued from this point on. A repeat can only be requested in the dialog screen. If the data from the failed delta request has already been updated to data targets, delete the data from the data targets in question. If you do not delete the data from the data targets, this could lead to duplicated data records after the repeat request.
Repeat delta update
If the loading process fails, the delta for the DataSource is requested again.
Early delta initialization : This is a advanced concept, but just for your information ...
With early delta initialization you can already write the data to the delta queue or to the delta tables in the application while the initialization is requested in the source system. This enables you to initialize the delta process, in other
words, the init request, without having to stop posting the data in the source system. You can only carry out early delta initialization if this is supported by the extractor for the DataSource that is called in the source system with this data
request. Extractors that support early delta initialization were first supplied with.

Inital load on standalone CRM

Similar Messages

Maybe you are looking for