Create huge number of IDOC

Hi All,
I am asked to create a file to IDOC scenario in PI. The problem is, the file will have around 200,000 records, 96MB. That means I have to get the 200,000 records from the file and create 200,000 PO IDOC at once. I know this is not possible. Does any one have this experience? How did you solve the problem?
Thanks a lot!
Charles

Few ways to implement this.
Though the file has huge number of records, you can tweak or control the number of idocs creating at the reciever side.
Refer michal blog for edit the occurence of target idoc structure to sent the number of idocs as per the need.
The specified item was not found.
https://wiki.sdn.sap.com/wiki/display/XI/File%20to%20Multiple%20IDOC%20Splitting%20without%20BPM
if your sender side is flat file then in the content conversion you set the parameter Recordsets per message like 100 or so.. so that you create 100 idocs each time from the sender message structure. Refer SDN forum for fcc parameters and sender fcc adapter scenario.
Refer this thread
Recordsets per Message in File adapter

Similar Messages

Create material number in Idoc

Hi experts,
I am new to create Idoc and ale.so please help me with basic steps.
I have two servers ECC6.0 and 4.7. I want to send the details like (mbrsh,mtart.maktx,meins) from 4.7 then i want to create the material number in ECC6.0 and i want to get the material number in sap4.7..for this what are all the steps i need to follow....from creation of function module to idoc....everything i need.....what parameters can i use in function module......help me please..

Hi,
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Maximum size of XML files and number of IDocs for IDoc receiver adapter

Hi Guys,
We have an XML file to IDoc scenario where XI picks up an XML file with multiple Customer records in it, it does a simple mapping and creates one DEBMAS06 IDoc per record in the XML file. All IDocs are sent in a single file in XML-IDOC format to IDoc adapter which then posts the separate DEBMAS IDocs to R/3.
a) What is the maximum size of XML files that XI can handle with mapping involved ?
b) What is the maximum number of IDocs in a single file that the receiver IDoc adapter can handle ?
The first time this interface runs almost 200,000 Customer records will be exported in one XML file.
Thank you.

Hi,
Well it is difficult to find out the maximum Size of xml messgaes that can be processed by XI and also Maximum number idocs an recevier Idoc adapter can handle.
This totally depends on your production system loads and the limits can be set totally on trail & error basis..
In my heavy loaded production system, i found out that the maximum size of the successfull messages after processing by XI is around 75 MB (seen in transaction SXMB_MONI). Whereas messages with size around 100 MB went into error.
I havent encounter any such limits with respect to Idocs.
I would suggest that you divide your data into smaller chunks and sent it part by part instead of sending it all once since you data size is huge.
You can vary your batch size as per your system load.
Regards,
- Deepak.

How can i organize a huge number of events?

I just began with mac and iphoto. I imported a lot of photos from windows (google picasa) in iphoto (>17000). Now I have a huge number of events, which i would like to sort by e.g. years and months. Within the years and months, the events should be placed.
Is this possible or what would you suggest to handle a lot of photos?
Thank you in advance for any helpful answer.
Alumsch

alumsch wrote:
I just began with mac and iphoto. I imported a lot of photos from windows (google picasa) in iphoto (>17000). Now I have a huge number of events, which i would like to sort by e.g. years and months. Within the years and months, the events should be placed.
Is this possible or what would you suggest to handle a lot of photos?
Thank you in advance for any helpful answer.
Alumsch
Assuming that you have events sorted by date (event menu ==> sort events) your events will be sorted by date & time - you can not create a substructure within events - it is a large flat set of photos
If you want a hierarchal structure use albums and folders - albums hold photos and folders hold albums or other folders - you also can use smart albums to instantly find all photos from a date or a date range - or the search window in the lower left
Events a a very basic, inflexible and pretty much automatic organization - just a starting point to hold photos
I generally merge trips into a single event and leave the other time based - others merge even more having events like 1st quarter 2010 etc
LN

Credit Memo request with reference to Billing Document number via IDoc

Hi,
I want to create credit memo request with reference to billing document number via IDocs.
I have tried through ORDERS05, but when I process I saw that it is only processing with reference to contract number or quotation.
So is any other way of creating credit memo request creation with reference to Billing document number via IDocs?
Thank you in advance.
Regards,
Santhi

Please Help... it is Urgent... Thank you

IDOC bundling number of idocs in one message

Hi
I am using IDOC bundling where I have one message with around 33,000 idocs inbound to PI. Can i break the number of idocs per message so that I can have 5,000 idocs in each message. Is there a paremeter that needs to be changed create a recordset of 5,000 idocs per message or less?
Also Can I do IDOC packaging when sending the above 33,000 IDOCs to SAP ?
Please advise.
Thanks,
Teresa

Hi Raj,
My connectivity is JDBC - PI - SAP.
I execute a stored procedure to pick up line items and do graphical mapping to conver to IDOCS. According to you the best way is to pick less line items at a time and conver to IDOCs?
Can i do IDOC packaging at sender side in my scneario though i am already doing IDOC bundling?
Thanks,
Teresa

I can create material using inbound Idoc of type MATMAS01, but not MATMAS05

I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
My system is ECC5.0. Thanks.

Hi, nagaraj
this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
In WE82, there are 5 records about Messagetype MATMAS:
     Message type   Basic type     Release
      MATMAS         MATMAS01        30A
      MATMAS         MATMAS02        30D
      MATMAS         MATMAS03        40A
      MATMAS         MATMAS04        46C
      MATMAS         MATMAS05        470
   I think it should be ok.
In WE57, there 2 records are exist:
   FM_name                 BasicType       MessageType
IDOC_INPUT_MATMAS01       MATMAS01         MATMAS
IDOC_INPUT_MATMAS01       MATMAS05         MATMAS
so I think all configurations should be ok.
Message was edited by:
        liu bin

Slow due to huge number of tables

Hi,
unfortunately we have a really huge number of tables in the ( Advantage Server ) database.
About 18,000 + tables
Firing the acitveX preview thru RDC, or just running a preview in the designer slows down to a crawl.
Any hints? ( Besides get rid of that many tables )
Thanks
Oskar

Hi Oskar
The performance of a report is related to:
External factors:
1. The amount of time the database server takes to process the SQL query.
    ( Crystal Reports send the SQL query to the database, the database process it, and returns the data set to Crystal Reports. )
2. Network traffics.
3. Local computer processor speed.
    ( When Crystal Reports receives the data set, it generates a temp file to further filter the data when necessary, as well as to group, sort, process formulas, ... )
4. The number of record returned
    ( If a SQL query returns a large number of records, it will take longer to format and display than if was returning a smaller data set.)
Report design:
1. Where is the Record Selection evaluated.
    Ensure your Record Selection Formula can be translated in SQL, so the data can be filtered down on the Server, otherwise the filtering will be done in a temp file on the local machine which will be much slower.
They have many functions that cannot be translated in SQL because they may not have a standard SQL for it.
For example, control structure like IF THEN ELSE cannot be translated into SQL. It will always be evaluated in Crystal Reports. But if you use an IF THEN ELSE on a parameter, it will convert the result of the condition to SQL, but as soon as uses database fileds in the conditions it will not be translated in SQL.
2. How many subreports the report contains and in section they are located.
Minimise the number of subreports used, or avoid using subreports if possible because
subreports are reports within a report, and if you have a subreport in a details section, and the report returns 100 records, the subreport will be evaluated 100 times, so it will query the database 100 times. It is often the biggest factor why a report takes a long time to preview.
3. How many records will be returned to the report.
   Large number of records will slow down the preview of the reports. Ensure you only returns the necessary data on the report, by creating a Record Selection Formula, or basing your report
off a Stored Procedure, or a Command Object that only returns the desired data set.
4. Do you use the special field "Page N of M", or "TotalPageCount"
   When the special field "Page N of M" or "TotalPageCount" is used on a report, it will have to generate each page of the report before it displays the first page, therfore it will take more time to display the first page of the report.
    If you want to improve the speed of a report, remove the special field "Page N of M" or "Total Page Count" or formula that uses the function "TotalPageCount". If those aren't used when you view a report it only format the page requested. It won't format the whole report.
5. Link tables on indexed fields whenever possible.
6. Remove unused tables, unused formulas, unused running totals from the report.
7. Suppress unnecessary sections.
8. For summaries, use conditional formulas instead of running totals when possible.
9. Whenever possible, limit records through selection, not suppression.
10. Use SQL expressions to convert fields to be used in record selection instead of using formula functions.
For example, if you need to concatenate 2 fields together, instead of doing it in a formula, you can create a SQL Expression Field. It will concatenate the fields on the database server, instead of doing in Crystal Reports.
SQL Expression Fields are added to the SELECT clause of the SQL Query send to the database.
11. Using one command as the datasource can be faster if you return only the desired data set.
      It can be faster if the SQL query written only return the desired data.
12. Perform grouping on server
   This is only relevant if you only need to return the summary to your report but not the details. It   will be faster as less data will be returned to the reports.
Regards
Girish Bhosale

Creating inbound Sales Orders IDOC within SAP

Hi,
I receive a flat file containing sales order information. I would like to create inbound Sales Order IDOCs from this flat file. I know I can use BAPI_SALESORDER_CREATEFROMDAT2 to create sales orders however I would like to retain the benefits of IDOCs e.g. error retention and re-processing.
There are a number of functions MASTERIDOC_CREATE* to create various IDOCs but I can't seem to find one for message type ORDERS. I know I can create a 'Z' version but would like to avoid that as much as possible as development budget is tight.
Any help would be greatly appreciated in the form of reward points.
Thanks and regards,
Liam

Hi,
Can u tell me the steps to create a sales order using idoc, i've created a bapi but thats a temprory use. I wanted to created a sales order automatically when a purchase order is saved.
Please let me know if u can help me, i wanted to do it using idoc
Regards
Sanju

Huge number of Managed Properties

I've recently started at a new company and inhertied the existing SharePoint Farm. I've looking at search as it seems quite slow crawling content. One thing I have noticed is that there is a huge number of Managed Properties >5000. There are
pages and pages like the one below.
There are only ~1800 Crawled Properties so I'm not really sure why there are so many Managed Properties.
I have noticed that the SharePoint and Office categories have the 'Automatically generate a new managed property' enabled. The farm uses a number of 3rd party addons and I'm not sure it they are responsible or not at this point or if they Require the
Automatically generate Properties option.
Just wondering if anyone had seen this or may have an idea?
Cheers

Hey Scott, thanks for replying.
The managed Property Mapping looks normal it's mapped to a single Crawled Property.
Although there are >4000 Managed Properties mapped to a single
Crawled Property which is weird.
I don't know where the Crawled property is coming from though. This is 2010 so I can't use the
SiteCollection property of the Get-SPEnterpriseSearchMetadataCrawledProperty command to filter. I'm not sure there is another way of figuring that out.
I'll probably end up trying to delete all of these Mapped Properties or Just create a new Search Service Application and start from scratch.

Creating contracts on backend - iDocs not even sent from SRM

Hi all
I'm having a bit of trouble configuring backend contracts and could use a little help from the experts.
Trying to create a contract from SoCo or bid invitation results in a success message informing a contract number, but idocs BLAORD and COND_A don't appear on WE02 on the backend. Checking on WE05 on SRM, no idocs are listed, so I'm assuming they are not even being created.
BAdIs BBP_DETERMINE_LOGSYS and BBP_CTR_BE_CREATE are implemented and active, logical systems and RFC destinations are defined correctly and organizational data is ok. Also backend POs are working fine. Please advice.
Best regards
Alvaro

Hello Alvaro,
for backend contract creation, there is no IDOC generated in SRM, but directy in R/3, but the function BBPV_CONTRACT_CREATE.
If an error occurs during this function call, you should get an error message in Application Monitoring.
You can access those monitors via the web, with role SAP_BBP_STAL_ADMINISTRATOR, or directly in SAP GUI with transaction RZ10.
Last option: debug the process
Rgds
Christophe
PS: please reward points for helpfull answers

Huge number of garbage collected objects

We're running a system here with the java heap set to 256mb and have noticed
that now and then, garbage collection takes a horribly long time to complete
(in the order of minutes, rather than fractions of a minute!). Something
like 3 million objects are being freed when the server is heavily loaded.
Has anyone else experienced this behaviour? Has anyone tested weblogic with
JProfiler/OptimizeIt and found any troublesome spots where many objects are
created? One potential place where this can be happening is in the servlet
logging. Since there is a timestamp that is a formatted date, my guess is
that a new Date object is being created, which is very expensive and hence
might cause many more objects that need to be garbage collected. Can any
weblogic engineers confirm/deny this?

Use vmstat to determine if you're swapping. sar would work too.
Swapping is definitely dictated by the OS, but an inordinate amount of
swapping activity just means you get to tune the hardware rather along
with the application.
Jason
Original Message <<<<<<<<<<<<<<<<<<On 2/21/00, 12:45:26 PM, "Hani Suleiman"
<[email protected]> wrote regarding Re: Huge number of
garbage collected objects:
Here are the results from running top on that machine:
Memory: 512M real, 14M free, 553M swap in use, 2908M swap free
PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
3035 root 50 59 0 504M 334M sleep 308:42 5.13% java
How to make sure I'm not swapping? I thought that kind of thing was dictated
by the OS...
Rob Woollen <[email protected]> wrote in message
news:[email protected]..
If GC takes on the order of minutes to run then I suspect that you
are
paging. How much physical memory do you have on the machine? Make sure
that
you are not swapping.
-- Rob
Hani Suleiman wrote:
We're running a system here with the java heap set to 256mb and have
noticed
that now and then, garbage collection takes a horribly long time tocomplete
(in the order of minutes, rather than fractions of a minute!).
Something
like 3 million objects are being freed when the server is heavilyloaded.
Has anyone else experienced this behaviour? Has anyone tested weblogicwith
JProfiler/OptimizeIt and found any troublesome spots where many
objects
are
created? One potential place where this can be happening is in theservlet
logging. Since there is a timestamp that is a formatted date, my guessis
that a new Date object is being created, which is very expensive andhence
might cause many more objects that need to be garbage collected. Can
any
weblogic engineers confirm/deny this?

Steps for creating a custom outbound idoc

Hi,
Can u please each and every step wise for the creation of the custom outbound idoc.
Thanks
Kiran Prasad.

friend before posting ur query, try to utilize the search tab in the forum, u can find the answer for ur query if not continue with postings.
Follow this link for step by step tutorial with screen shots
http://www.****************/Tutorials/ALE/ALEMainPage.htm
1. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
u2022 From transaction WE30 or WEDI go to Development -> IDOC Types.
u2022 Enter ZDEBMASZ for Object Name.
u2022 Click on IDOC Type.
u2022 Click on Create.
u2022 Enter DEBMAS02 for Basic IDOC type.
u2022 Enter ZDEBMASX for extension type.
u2022 Enter a description.
u2022 Enter.
u2022 You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
2. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
u2022 Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
u2022 Click on Display <-> Change.
u2022 Click on New Entries.
u2022 Enter DEBMAS for message type.
u2022 Enter DEBMAS02 for Basic IDOC type.
u2022 Enter ZDEBMASX for extension type.
u2022 Enter your SAP R/3 release number for Release.
u2022 Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
3. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
u2022 From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
u2022 For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
u2022 The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
u2022 From transaction WE30 or WEDI go to Development -> IDOC types.
u2022 Enter ZDEBMASX for Object name.
u2022 Click on Extension Type.
u2022 From the Development Object menu select Check.
u2022 Repeat the operation for IDOC type ZDEBMASZ.

Implementing PaaS (CloudFoundry/BOSH) feeds a huge number of (unwanted) ProtectionServers into DPM

Hi
We have a Hyper-v cluster with VM's on Cluster Shared Volumes, we are using System Center (2012 R2) VMM and DPM for backing up the core infrastructure and a selection of vm's from some of our VMM clouds.
Ongoing work is to implement a PaaS with Hyper-V/System Center - with use of CloudFoundry/BOSH. Due to a lot of unity tests many short lived vm's are made that we never want to backup with DPM. It looks like that the DPM Agent on the Hyper-v hosts in the
cluster feeds all vm's that it sees into DPM as a ProtectionServer - even though these VM's do not have any DPM Agent installed.
Doing this SQL in the DPM Database:
SELECT count(*) FROM [DPMDB_MyDPM].[dbo].[vw_DPM_Server]
Gives 5531 entires. A huge number of these entires are from the PaaS CloudFoundry/Bosh created VM's in the IaaS. These are VM's that never have been backed up by DPM (Or have any DPM agent installed).
We see the same with use of powershell:
PS C:\> $ps = Get-ProductionServer | Where-Object {$_.Name -like "*bosh_vm_being_created*"}
PS C:\> $ps.length
5294
PS C:\>
* The huge number of (unwanted) Production Servers in our DPM causes that our DPM is going slower and slower. And we see that our DPM SQL Database is working more and more. Today we are only taking backup of around 20 VM's, the SystemCenter MSSQL and a few
hosts with DPM agent.
Question 1 - How can we remove these unwanted ("bosh_vm_being_created") ProductionServers from our DPM? They do not have any DPM agent installed, they have no recovery point in DPM. But still they are listed in DPM as a ProductionServer. Why?
Question 2 - How can we configure DPM to filter out these PaaS/CloudFoundry/Bosh VM's so that they do not reach the DPM system?
Br. Rune

Hi
Unfortunately I have no solution on my case yet. The number of ProductionServers in our DPM server is growing and growing. And our DPM is going slower and slower.
PS C:\> $ps = Get-DPMProductionServer -DPMServerName <DPMhostname>
PS C:\> $ps.length
8525
PS C:\>
It must be an purg-job that is not cleaning out old VM's (objects) from the DPM server I guess. I our VMM we only have around 200 VM's. So most of the ProductionServers in our DPM is old VM's that no longer exist.
When we try to use
Remove-ProductionServer.ps1 powershell to remove one of these ProductionServers - we get an error because the VM do no longer exist (and the VM do not have any agent installed).
Do anyone have any experience with this?
Br. Rune

Co88 - for huge number of production orders -running for hours

Hello All,
I have a issue, in our manufacturing plant, we have huge number of production orders created every day, almost 1200 per day. During month end it takes almost 8 to 10 hours for running settlement, we find very difficult in doing month end closing. We also attempted parallel processing, it errors out.
I heard that, the co88 program looks each order by order checking the status, like closed, and thats the reason, its time consuming, i am not sure how far its true.
I am sure this general issue, people might have come across, can anybody share their experience. How to overcome this issue to run the settlement with possible minimal time, is there any note. please guide me
thanks
best regards
gj

Yes, this is a generic issue. Most clients manage by marking the orders as closed/deleted, so that these orders are not considered for period end settlement.
Also consider note 545932, and search notes fo further help.

Create huge number of IDOC

Similar Messages

Maybe you are looking for