IDOC Packing : Doubt

Hi Guys,
I refered IDOC packing blog in Sender ECC system i entered Transaction WE20
Outbound Options --> Output Processing ---> (Transfer Idoc Immed / Collect IDOCs)
Presently am using --> Transfer Idoc Imme --> Pack Size comes by default (1)
----> Collect IDOCs ---> Pack Size can be change
I hope above config should be done for Packing , correct me.
Also i hope by doing above would increase my performance but do the record get's transfered immediately,
Am bit confused can any one alobrate the above and correct me if any out of path
Thanks in advance
Regards
Srinivas

> Presently am using --> Transfer Idoc Imme --> Pack Size comes by default (1)
>
> ----> Collect IDOCs ---> Pack Size can be change
>
Yes you can define your own packet size
> I hope above config should be done for Packing , correct me.
>
You are Correct.
> Also i hope by doing above would increase my performance but do the record get's transfered immediately,
As soon as the packet size will be reached it will get transfered. Let's say if you defined packet size as 500, so as soon as 500 idocs will be collected, it will be get transfered.
Regards,
Sarvesh

Similar Messages

Idoc packing in sap pi 7.3

Hi Gurus
i have check the check box with multiple idocs insinle message in sender idoc adpter which is running on java stack.
is idoc packing is supported in sap pi 7.3 in idoc_aae running on java stack.
if it is working on java stack please help me.

Hi,
What is the error that you're getting...You can use Idoc packaging in java idoc adapter(IDOC_AAE). If you check multiple idocs in single XI message (IDOC xml) checkbox in the Idoc sender communication channel, packaging will be activated.
Please refer this
http://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/4096a6b3-3dc3-2d10-bf87-f63d5340a916
Configuring PI 7.30 Java IDoc Adapter
Regards,
Priyanka

IDoc packing with PI 7.1 EHP1

Hello,
how does IDoc packing (EHP1) work within a IDoc sender channel? Has anybody already tried it? Can I simply recieve "collected" IDoc from ECC (e.g. invoic IDocs) which are not splitted by IDoc adapter? So that I do not have to use a collect BPM any more?
Thanks!
Christoph

> that means I have to "create" an IDoc sender channel to receive IDocs from ECC? How can I define whether IDocs should be received via this IDoc sender channel or via the "standard" IDoc adapter?
>
Yes, you do have to create an IDOC sender channel. The IDOC packaging option in the CC distinguishs a standard idoc channel from idoc channel with packaging.
> How to define the IDoc package size when I don't know how many IDocs will be sent from ECC to PI?
I would recommend you to watch the below video from the timeslot 00:45, you will http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/40a412a0-9501-2c10-cb83-f124e23d5373&overridelayout=true
Pooja

IDOC bundling & IDOC packing

Can you explain with examples for IDOC bundling & IDOC packing

Hi
IDoc bundling is like sending multiple IDoc ...
Ex Scenario: U have file containing Multiple Sales order and for every sales order u are generating an IDoc so in the mapping u change the occurance of IDoc. Consider that the occurance of IDoc is 1-1 and now by exporting the IDoc and making changes to the occurance as 1- unbounded in the XSD. Now by importing this xsd we can send multiple IDoc this is IDoc bundling.
IDOC Packaging on outbound side
IDoc Packing is someting Viceversa to IDoc Bundling.
Ex Scenario: Multiple IDoc each containing a Sales Order is sent to XI and we want a single file to be containg all the IDoc sales order details. So we collect all the IDoc sent by R/3 for a perticular time or condition and do a mapping to generate a single file.
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
> 3) IDoc Bundling,
/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Please provide points if helpful
SD

Idoc Packing

Hi experts.
We have a SOAP --> IDOC escenario.
The problem is that the message received in SOAP Adapter sometimes is huge so I have to create loads of idocs. In this situation I have a problem when idocs are sent to SAP Backend System because of an overlflow in lock table (The idocs remains in PI in tx SM58 with error status) so I'd like to pack the idocs and sent them little by little to SAP Backend System to avoid this overflow.
For instance if a create a 30MB package with N idocs I'd like to send them to SAP Backend in smaller packages in serveral times instead in once.
I've seen blogs to collect a group of idocs to send in one packege but not this.
Could I achive this? How?
Thanks a lot.

Thanks everybody but that's not what I'm looking for.
The issue is:
After mapping I have a package that contains N idocs. Could I send this N idocs to ERP System in N smallerpackages avoiding in this way to make only one RFC call?
I know how to collect idocs without BPM to send to ERP with packing but not the inverse and I dont know if that could be done (Im working with 7.0. In 7.1 I know that it can be done).
Any idea?
If I had a File_to_Idoc scenario I wouldn't have this problem because I could manage the size of the package in the sender file adapter.....
Regards and thank you so much.
Edited by: Christian Abad Chico on Mar 16, 2011 5:04 PM

IDoc related doubt .......Please see..

Hi all,
What is message in Idoc? Please tell in layman terms. Is it part of the data records? Please point me to related files or threads.
Thanks,
Charles.

Hi,
The Message type are mornally assign to SAP document type (IDOC). A message type represents a business function ( Purchase order data, Invoivce data etc). The technical structure of the message type is the IDoc type.
An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).
The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).
Example
The message ORDERS (= message type) identifies purchase orders (outbound) and sales orders (inbound).
Check transaction WE81, for Message type in SAP.
Also, follow this link for more infomation related to IDOC processing
http://help.sap.com/saphelp_46c/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Check this lin for information about "Distribution Using Message Types".
http://help.sap.com/saphelp_46c/helpdata/en/78/2174a351ce11d189570000e829fbbd/frameset.htm
Let me know if you need any other information.
Regards,
RS

File to IDOC Scenario - Doubt in RFC Destination

Hi all,
I m working on a File - IDOC Scenario. I got a IDX1 error Also when I try to import IDOC in IDX2, I got I:000 error message(No more information was given) . When I checked the RFC destination, Test Connection works fine. But Remote Logon didnt work, since the target system is not a Trusted System
Is it necessary to make the Target System, a Trusted System ? (For enabling Remote Logon)

Hi ,
There might be some problem with the R3 user that u r using...
For some versions of R3 it is required that the password be in CAPS for making an RFC connection...
I knw this sounds weird but even i had this problem....
Also chk if the XI user has RFC priviliges..
reward points if helpful
PrashANt

IDOCs - Simple doubt in INBOUND DELVRY. IDOC-DELVRY03, Process code isDELV?

Hello Experts,
Our SAP system receives the Inbound IDOC for Delivery from Gentran.
Further details are,
Process code: DELV
IDOC type: DELVRY03
Message type: SHPCON
Message code: TOC
Parther profile: Account # of Ship To party
So, my requirement is that,
If this Inbound Delivery IDOC contans the Message Code as TOC, I need to insert/add my logic
so, let me know that,
1) Request u that, let me know How to go ahead, becoz am new IDOCs, like, Is I need to look for the any Usre Exit? I mean, At Wht point I need to add my code in this whole process?
thank you
Edited by: Srinivas on Jun 29, 2008 11:15 PM

Hi Srinivas,
Use the below user exit for creating a STO order.
CALL CUSTOMER-FUNCTION '003'
       EXPORTING
            IDOC_CONTROL        = IDOC_CONTRL
            IDOC_DATA           = IDOC_DATA[]
            DELIVERY_HEAD       = S_KOKO
            DELIVERY_ITEM       = T_KOPO[]
            PACKING_HEAD        = T_VSEK[]
            PACKING_ITEM        = T_VSEP[]
            PROCESSING_STATUS   = F_STAT
       IMPORTING
            WARNING_IGNORE      = F_FLAG
       CHANGING
            PROCESSING_PROTOCOL = T_PROT[]
       EXCEPTIONS
            OTHERS              = 0.
Because by the time you get to this point, the delivery document is created. I believe you need to create the STO order only once the delivery document is created.
Thanks,
Mahesh.

On Idoc small doubt

In the Idoc we will transfer data between production servers Ok. suppose If I am transferring the vendor master data, between which system we will transfer ( I think one is SALES system and another one I don't know)
If I am transferring Customer master data between which system we will transfer plz tell me
This one

In real time usually master data is transfered through ALE technology with in the organization.
I will explain one scenario.
In my company Master data is stored in one server that is central system, company having branches all the countries, each country is maintaining their own server, and every one don't required all the customer / vendor details.
with whom they are doing bussiness their addresses are maintained in their server, if they want to add any other customer details which is existing in central system then get the information in form of idoc.
if any changes are there in customer details u can send idoc to all system who are using that customer from central system.
i hope u understood.
Reward points if useful
Madhavi

OSS note 778805 to correct IDOC packed HU wrong weight

Std system behavior does not validate gross weight-net wt-tare (GRBEW-NTGEW-TARAG) received by IDOC.
OSS note 778805 modification changes this, but how? Does it recalc gross wt based on net and tare? Reluctant to implement even in DEV without better understanding.

Bom dia Marc de Ruijter,
Não dá para ler sua thread, mas imagino que seu validador esteja desligado.
No GRC vá em SPRO --> SAP GRC Nota Fiscal Electronica --> Configure System Response for Each Tax Number (CNPJ)
Para ligar/desligar o Validador basta clicar no check box na coluna Validation.
Observação: Para correto funcionamento do GRC deve-se sempre utilizar o validador ligado.
Após isto refaça seu teste, é provável que você receba um erro de validação para a NF-e. Veja em GRC Web monitor -> NFe Detailed View -> Validation History.
Atenciosamente,
Fernando Da Ró

Idoc Status doubt...

Hello,
If an Idoc(Inbound) is in status 64 (Idoc ready to be passed to application) is there any way to force it to any other status so that it will not be processed by the backgroung job(running for RBDAPP01)...?
Is it possible to force an inbound idoc to other status...?
We need to stop the idoc before its been processed by Scheduled background job...
Thanks,
Larry

Use this:
<code>
REPORT z_idoc_status.
TYPE-POOLS:
slis.
TABLES:
edidc.
TYPES:
BEGIN OF out_type,
 docnum LIKE edidc-docnum,
 mestyp LIKE edidc-mestyp,
 status_old LIKE edidc-status,
 status_new LIKE edidc-status,
END OF out_type.
DATA:
wa_out TYPE out_type,
out TYPE STANDARD TABLE OF out_type.
DATA for ALV GRID VIEW
DATA: fcat TYPE slis_t_fieldcat_alv,
 wa_fcat TYPE slis_fieldcat_alv,
 alv_layout TYPE slis_layout_alv,
 alv_variant TYPE disvariant,
 alv_grid_title TYPE lvc_title,
 alv_sort TYPE slis_t_sortinfo_alv,
 wa_alv_sort TYPE slis_sortinfo_alv,
 alv_report_id LIKE sy-repid.
SELECTION-SCREEN BEGIN OF BLOCK idoc WITH FRAME TITLE text-001.
SELECT-OPTIONS s_docnum FOR edidc-docnum.
SELECT-OPTIONS s_mestyp FOR edidc-mestyp.
SELECT-OPTIONS s_staold FOR edidc-status.
PARAMETER p_stanew TYPE edidc-status.
PARAMETER p_update AS CHECKBOX.
SELECTION-SCREEN END OF BLOCK idoc.
START-OF-SELECTION.
SELECT
 docnum
 mestyp
 status
INTO (wa_out-docnum
 ,wa_out-mestyp
 ,wa_out-status_old
FROM edidc
WHERE docnum IN s_docnum
 AND mestyp IN s_mestyp
 AND status IN s_staold.
 wa_out-status_new = p_stanew.
 APPEND wa_out TO out.
ENDSELECT.
IF p_update = 'X'.
 LOOP AT out INTO wa_out.
 UPDATE edidc
 SET status = p_stanew
 WHERE docnum = wa_out-docnum.
 ENDLOOP.
ENDIF.
CLEAR wa_fcat.
wa_fcat-fieldname = 'DOCNUM'.
wa_fcat-ref_tabname = 'EDIDC'.
wa_fcat-ref_fieldname = 'DOCNUM'.
wa_fcat-key = 'X'.
APPEND wa_fcat TO fcat.
CLEAR wa_fcat.
wa_fcat-fieldname = 'MESTYP'.
wa_fcat-ref_tabname = 'EDIDC'.
wa_fcat-ref_fieldname = 'MESTYP'.
APPEND wa_fcat TO fcat.
CLEAR wa_fcat.
wa_fcat-fieldname = 'STATUS_OLD'.
wa_fcat-seltext_l = 'Status alt'(002).
wa_fcat-seltext_m = 'Status alt'(002).
wa_fcat-seltext_s = 'Status alt'(002).
APPEND wa_fcat TO fcat.
CLEAR wa_fcat.
wa_fcat-fieldname = 'STATUS_NEW'.
wa_fcat-seltext_l = 'Status neu'(003).
wa_fcat-seltext_m = 'Status neu'(003).
wa_fcat-seltext_s = 'Status neu'(003).
APPEND wa_fcat TO fcat.
alv sortierung
CLEAR wa_alv_sort.
wa_alv_sort-spos = 1.
wa_alv_sort-fieldname = 'DOCNUM'.
wa_alv_sort-up = 'X'.
APPEND wa_alv_sort TO alv_sort.
alv Ausgabe
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_callback_program = alv_report_id
 i_grid_title = alv_grid_title
 is_layout = alv_layout
 it_fieldcat = fcat
 i_save = 'A'
 it_sort = alv_sort
 is_variant = alv_variant
 TABLES
 t_outtab = out
 EXCEPTIONS
 program_error = 1
 OTHERS = 2.
</code>
You can manipulate the status of each idoc.

XI 3.0 Service pack doubt

Hi Friends..
        I have XI 3.0 and i have the patch to sp11... now i am planning to update SP 19...So i have the service marketplace id also. i am trying to download the SP ..their ..source SP is : SP11 and target is SP19 i choosen..then it shows aother step...like..conversionagen...IGS...etc...i need to choose these things are continue to step 3..What i need to do.. Please help me..
Regards,
Kumar

hi
Just go through this may be useful.
1)
Is it possible to directly deploy the SP19 or.. we need to download the SP10, SP11, SP12...SP17..SP19..
>>> you will have to go from SP10, SP11, SP12 etc - SP19
3) Where i can download this SP..I have Service marketplace access..
may i have the URL for that..
>>>
https://websmp102.sap-ag.de/swdc
use the left side menu to search for what you need.
2)
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000595001&_SCENARIO=01100035870000000202&
Browse through to find your correct version.
3)
Log on Here:
https://websmp105.sap-ag.de/~sapdownload/011000358700001672772004E/NW_Start.htm
Select Source Stack. Select Target Stack.
Select Usage Selection and follow the instructions!
Please read the Support Package Stack documentation specified for each Stack before you apply any Support Packages or Patches of the selected SP Stack.
The corresponding documentation and further specific information about SAP NetWeaver '04 Support Package Stacks can be found by follow the link https://websmp203.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000650682&
SLD:
Product: Represents a collection of all versions of a product. A product is a unit that can be delivered, is visible to the customer, and that is installable and renewable. In an SAP environment, a product corresponds to an SAP technical component.
Product Version: Represents a particular version of a product.
       Software Component: Represents a collection of all versions of a software component. Software components represent the reusable modules of a product. They can be upgraded or have patches installed.
        Software Component Version: Represents a particular version of a software component.
        Software Feature: Represents a particular aspect of the product functions. It is a logical link between Product Version and Software Component Version.
All IB Repository objects are arranged in
1. Software components.
2. Namespaces.
You create the SWC in SLD, import them to IB Repository. SWC itself are arranged in products. So, a product can have 1-n SWC. It stands for a deliverable unit. You should design a SWC as something belonging to a system and indeed you can associate products/ SWC to a business system. This control the selecting of interfaces at configuration time.

IDOC Receiver problem with 7.11 and ECC6

Hello,
we have a IDOC_2_IDOC scenario on old XI system which worked fine.
We are moving now to PI7.11 and get the problem, that all IDOCs in the receiving ECC6 system
go to status 51 "No status record was passed to ALE by the application"
It seems to be a problem of processing of too many IDOCs at the same time,
because if there is enought ime between the IDOCs the the procsing in ECC6 works.
Only if too many IDOCs are sent from PI to ECC6 then I get this error.
I have checked aRFC and tRFC options in SM59 but there is no difference.
IDOC packing is not activated on sending system and on PI.
At the moment the scenario should work as is worked on 7.0......
Any ideas which setting is different or where to look?
best regards
Werner

Hello,
which ALE settings do you mean???
on PI or receiving ECC6
PI:
here we only use SM59, IDX1, IDX2.... for IDOC adapter
ECC6: only partner profile INBOUND PARAMETER
On the sending R/3 system I can not change something.....and there was no change.
best regards
Werner

IDoc waiting in XI monitoring

Hi,
I am working on a idco to file scnario. I have an issue here.
I trigger an idoc ,from the erp and in the XI monitoring (SXMB_MONI) , the status of the IDOC is LOG VERSION .
Then i trigger nine more idocs from ERP. ONce the 10th idoc reaches the XI , the procesiing of all the 10 idocs take place.
This is kind of collective processing .
How can i deactivate this .? So that single processing of idoc shd be possible.

Hi,
like mentioned by Boopathi and Riyaz it could also be the Idoc packing in idxpw.
Here is a blog about it:
XI:Idoc Message Packages
But this should normally only the case if it was configured before.
Regards
Patrick

RBDAPP01 going into SLEEP Mode and Idocs still in 64 status

Hey all,
I have a Inbound Idoc interface which is being processed using RBDAPP01 Program. The Issue I am facing is that the job running the rbdapp01 program goes into sleep mode even though there are idocs present in 64 status. I tried to debug the work process using SM66 but it does not open any debugging window although it says debugging started. If I cancel the Job and run it again it processes those Idocs Any input on how one can resolve this issue?
Thanks.

Hi Aparna,
Here is extract from SAP material on running RBDAPP01 transaction and possible reasons for delay in processing. HOpe this can help you.
To automate the treatment of IDocs, you must run the ABAP program RBDAPP01 (transaction BD20) in job. This program has a very good option for parallel processing which can reduce a lot the time required for treatment. However use it carefully and make sure you set a packetsize high enough to avoid that your SAP system be overwhelm by demands for available dialog tasks (don't forget one dialog task is monopolized per IDocs packed to treat).
Best Regards,
Krishna

IDOC Packing : Doubt

Similar Messages

Maybe you are looking for