Partners profile - outbound parameters - package size ?

My scenario: IDOC(R/3)-XI-File.
R/3 settings: WE20 - While filling out outbound parameters in partners set up i am getting error "<b>please enter a value for package size</b>" highlighting <b>Receiver port</b> in red. My receiver port is tRFC type whose RFC destination would be XI server.
I have created logical systems(SALE) for sender(R/3) and receiver(XI) as well assigned them to clients.
Please help.

Hi Bhavesh,
This is what exactly I did and I ended up getting this error message. I did some research on how to generate partner profiles on sdn.
"transaction SALE), choose Modeling and Implementing Business Processes ®Maintain Distribution Model and Distribution Views (transaction BD64)."
So,I have created a model view called "EC4_TO_PI1".
Then I chose Environment----> Generate Partner profiles. Now, I have to select two model views. (From & To).  From Model View I have selected the above model view " EC4_TO_PI1". I am not sure about TO field.
Can you please guide me to helpful documentation ? I am not even sure what is distribution model is. Thank you for your help.
By the by, I have already created logical systems for sender(R/3) and receiver(XI). fyi.

Similar Messages

  • Partnet Profiles : Outbound Parameters

    Hello -
    When i try to create outbound parameters in Partner Profile in R/3, sometimes i don't get the packet size, i just see only the Receiver Port.
    Any ideas why i could not see this option?

    Hi Tirumal,
    when u enter once the field gets activated. when u click on enter again you will get a message saying
    Please enter a value for packet size.
    If your radio button for 'Output mode' is Transfer Idoc immediately then u need not fill this value.
    If the radio button is on collect IDoc you have to fill in this field.

  • Partner Profiles: Outbound parameters

    I want to send a IDOC ORDERS05 to SAP ECC6.0.
    I have a partner type LS.
    In outbound parameters I can not define message type ORDERS ???
    The error message ==> "Logical message ORDERS does not exist"
    Anyone can give some tips?
    Thanks a lot!

    when you send IDOCs from XI to ERP you don't use WE20
    it's a competely different procedure
    also XI does not have ERP idoc types (that's why
    you cannot choose it in WE20)
    check out my book to find out step by step how to do it:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Package Size parameter in Partner Profile

    Hello guys,
    I'd need your advice. We have 2 systems (SAP and Non-SAP) and we need to connect them by mean of HR-PDC interface (IDoc communication is supported). We can create new Partner Profile in SAP and we can add a few IDoc types as Inbound Parameters of the partner profile. Then it is possible to define maximal package size for several IDoc types. I suppose that the Non-SAP system reads the Partner Profile and the "Package Size" parameter for the particular IDoc type before it sends some IDoc to SAP system. IDoc's size is limited by the parameter.
    And now our problem. We need to insert XI between these 2 systems. XI should only forward IDocs and nothing else. How could I set up limitation of IDoc's size? Do you thing that following scenarion could be working?
    I would define Partner Profile in XI same way as in the previous case in SAP. XI is configured to process IDocs in Integration Server by means of IDoc adapter. My expectation is that the Non-SAP system would read the partner profile in XI (including "Package Size" parameter) and then it would send IDoc to XI. Then XI would process the received IDocs in IDoc adapter.
    How can be "Package Size" parameter useful for inbound IDocs?
    Best Regards,

    Hello ,
                Check the blog below

  • WE20 message No Package size option

    I'm maintain partner profile-->outbound parameters, but I can't find a option to set the package size.
    NetWeaver2004s(in the SAP Discovery system)
    Anybody can help me?

    As far as my knowledge, Package size (collect idoc)is generally not visible when, either ur messge type or basic type is not mentioned correctly,
    Also check ur receiver port.
    Message was edited by:

  • Value of package size issue with partner

    Iam trying to configure idoc type in the partner, but when i try to save it,  is giving the following error
    "Please enter a value for package size".

    Hi Kalyan,
    Check we20 (partner profiles) and the mode (in outbound) it it is collect you need top specify a size for package
    Check this thread too
    Re: ale/idoc setting
    Edited by: S.R.Suraj on Oct 12, 2009 12:09 PM

  • Maximum package size for data packages was exceeded and Process terminated

    Hello Guru,
    When i am execute the process chain i got this message Maximum package size for data packages was exceeded and Process terminated,any body help to me in this case how can i proceed.
    Thanks & Regards,

    When the load is not getiing processed due to huge volume of data, or more number of records per data packet, Please try the below option.
    1) Reduce the IDOC size to 8000 and number of data packets per IDOC as 10. This can be done in info package settings.
    2) Run the load only to PSA.
    3) Once the load is succesfull , then push the data to targets.
    In this way you can overcome this issue.
    You can also try RSCUSTV* where * is an integer to change data load settings.
    Change Datapackage size for extraction, use Transaction RSCUSTV6.
    Change Datapackage size when upload from an R/3 system, set this value in R/3 Customizing (SBIW -> General settings -> Control parameters for data transfer).
    IN R/3, T-Code SBIW --> Genaral settings --> Maintain Control Parameters for Data Transfer (source system specific)
    Hope this helps.

  • How to specify PACKAGE SIZE for to RFC_READ_TABLE from PyRFC?

    I'm trying to use PyRFC to extract large tables via RFC_READ_TABLE (due to an uncooperative/unsupportive basis team).
    I know that RFC_READ_TABLE supports calling it with PACKAGE SIZE since ERPConnect does it by default.
    In Python for Basis (Part 1), I learned how to specify an Open SQL where clause using the OPTIONS:
    result ='RFC_READ_TABLE',
                           OPTIONS = [{'TEXT':where_clause}])
    Is there a way, and how to specify PACKAGE SIZE in this case?

    the package size works, but you need to call the function module multiple times in a loop. Here's an excerpt of the attached script:
    recordcounter = 1          #needs to be >0 to get the while loop going
    iteration = 0              #the number of times the function module got called
    while recordcounter > 0:  #as long as the function module calll returns rows...
        tempresult ='RFC_READ_TABLE',             
                                ROWSKIPS=iteration*fetchsize,  #defines the number of rows to skip
        iteration=iteration+1  #increase the iteration
        data = tempresult['DATA']    #assign the returned rows to a variable
        if len(data) > 0:      #have there been any rows?
            for row in data:      #Do something with them
            recordcounter=0    #set recordcounter to 0 to end the while loop.
    The script is far away from being perfect. It doesn't deal with RAW fields and the data types it returns are all strings. It does what I needed it to do but it may not be sufficient for what you may be trying to achieve.
    Best regards

  • BD64 - generate partner profile - outbound parameter; wrong receiver port

    Hi all,
    I'm using a distribution model (transaction BD64) for creating partner profiles in my system.
    This works fine, exept for one thing.
    The receiver port used in the outbound parameter is wrong.
    It's using the tRFC port of the destination system instead of the tRFC port of the SAP XI/PI system.
    If I send an Idoc it's now going directly to the destination system instead of going to XI/PI first.
    I could modify this manually (which is a lot of work), but I would like to know how SAP determines which tRFC port is used when generating the partner profile and creating the outbound parameters.
    Can anybody help me with this?

    According to my knowledge, if you have a receiving logical system name is same as the RFC destination name, then the SAP will take the RFC destination properly and will generate the port automatically (for Ex: if you have a port A00..12 then it will create a port A..13). the generated port will be used in partner profile.
    Give a try by assign the RFC destination (The receiving logical system name and RFC destination name should be same) for a port and use it while generating the partner profile by using BD64 or SALE.
    Venu V

  • Info on package size

    I would like to understand what does this setting means in infopackage
    Maximum size of a data packet in kByte = 50000?
    How do I determine what is the package size that is going to come from the source system? Is there any documentation or notes that tells what the suitable package size is?
    Number of data packets per Info-IDoc = 10
    How does records get divided per package? On what logic?
    I extracted the data into PSA.
    DP 1 = 8000 records
    DP2 = 9500
    DP3 = 8400.
    The number of records is not same in all the packages. How does it work?

    The individual records are sent in packages of varying sizes in the data transfer to the Business Information Warehouse. Using these parameters you determine the maximum size of such a package and therefore how much of the main memory may be used for the creation of the data package.
    SAP recommends a data package size between 10 and 50 MB.
    if you transfer a lot of fields, you can transfer less lines...
    if you transfer less fields, you transfer more lines,...
    more info :

  • Distibution Model- Outbound parameters for message type could not be found

    Hi SRM Gurus,
                          Have you ever encountered this error while buidling Distribution model in BD64 -
    When I try to generate partner profile, I am getting this error-
    Outbound parameters for message type BBPCO BBPCO01 could not be created
    Partner not found in partner table
    This error is occuring for all message types.
    Please let me know the solution if anyone has encountered this error before.
    Thanks & Regards

    Are you geting this error while generate partner profile?
    hope your sender and receiver logical system are correct.double check.
    OUTPUT MODE - tRANSFER idoc immediately option
    connectivity between both sytems are ok.
    did you save modelview ?
    now ports automatically created . check we21 ,we20..
    check your sm59 rfc destination? what type connection you made ? hope you maynot do mistake. howevercheck itup.
    ask basis consultant assistance why ports anot genrated for backend system after you executed
    tbd05 - do yo have entry ?

  • Performance : how to detrmine the package size during a select

    When you do a select using package size, how to determine the value of the package size.
    Thanks for your help

    Hi marie,
    1. When you do a select using package size
    Its done when number of records is very high.
    and we don't want to fetch all records,
    2. At that time, we fetch records in BUNCHES / PACKAGES.
    3. Just copy paste to get a taste of it.
    REPORT abc.
    DATA : ctr TYPE i.
    selection screen.
      SELECT * FROM t001
      INTO TABLE t001
      PACKAGE SIZE 5 .
        ctr = ctr + 1.
        WRITE :/ '----
    Loop Pass # ' , ctr.
        LOOP AT t001.
          WRITE :/ t001-bukrs , t001-butxt.
    amit m.

  • How to understand "outbound parameters" and "inbound parameters" in WE20?

    How to understand "outbound parameters" and "inbound parameters" in transaction code:WE20? Which side is based to set the outbound/inbound parameters?
    As I can only set "outbound parameters" for the both partner type:customer and vendor.
    so, When do we need to set the parameter "inbound parameter"?

    If you deals with inbound IDoc processing then you need only to maintain partner profile for inbound parameter.
    However, if you deal with outbound IDoc processing then you need to setup partner profile for outbound parameter.
    In special case, you may need to setup both inbound and outbound parameters for example the sender needs to have confirmation or acknowledgement for completion of inbound IDoc processing.
    Please check this links and should help you to learn/start with ALE.
    Also you can check this online document for ALE and IDoc.
    Hope this will help.
    Ferry Lianto
    Please reward points if helpful.

  • Increase data package size

    I'm using a flat file datasource to load data from the BW server into a cube.  When I load a file containing 9000 records, the data package size is 1000.  I'm trying to improve the load time and would like to increase the data package size to 2000.
    I made an entry to specify 2000 records for my flat file source in SBIW -> Maintain Control Parameters for Data Transfer.  My file still loads with 1000 records in the data package. 
    I've also tried changing the setting on the infopackage itself, but it keeps telling me the max is 1000.
    Any suggestions?

    the settings you maintained in SBIW is for Other BI system not for Current System. whiel you exchange data between your current BI system with other BI System, then you need to maintain in SBIW.
    If you want to change for current system, you need to maintain in SPRO not SBIW. i can't tell you the exact navigation. it will be under "Links to Other System"
    If you are on BI 7.0, follow the below navigation....
    SPRO --> F5 -->SAP Netweaver -> BI --> Links to Other Systems -->Maintain Control Parameters for Data Transfer.
    Let me know if you need any information.
    Nagesh Ganisetti.

  • Data package size

    What is the basic difference between RSCUSTV6 & SBIW->General setting ->Maintain Control parameters in relation of modification of data package format.

    Just see the help on
    Maintain Control Parameters for Data Transfer:
    1. Source System
    Enter the logical system of your source client and assign the control parameters you selected to it.
    You can find further information on the source client in the source system by choosing the path
    Tools -> Administration -> Management -> Client Maintenance.
    2. Maximum Size of the Data Package
    When you transfer data into BW, the individual data records are sent in packages of variable size. You can use these parameters to control how large a typical data packet like this is.
    If no entry was maintained then the data is transferred with a default setting of 10,000 kBytes per data packet. The memory requirement not only depends on the settings of the data package, but also on the size of the transfer structure and the memory requirement of the relevant extractor.
    3. Maximum Number of Rows in a Data Package
    With large data packages, the memory requirement mainly depends on the number of data recrods that are transferred with this package. Using this parameter you control the maximum number of data records that the data package should contain.
    By default a maximum of 100,000 records are transferred per  data package.
    The maximum main memory requiremen per data package is approximately 2  Max. Rows 1000 Byte.
    4. Frequency
    The specified frequency determines the number of IDocs that an Info IDoc is to be sent to, or how many data IDocs an Info Idoc describes.
    Frequency 1 is set by default.. This means that an Info Idoc follows every data Idoc. In general, you should select a frequency between 5 and 10 but no higher than 20.
    The bigger the data IDoc packet, the lower the frequency setting should be. In this way, when you upload you can obtain information on the respective data loading in relatively short spans of time .
    With the help of every Info IDoc, you can check the BW monitor to see if there are any errors in the loading process. If there are none, then the traffic light in the monitor will be green. The Info IDocs contain information such as whether the respective data IDocs were uploaded correctly.
    5. Maximum number of parallel processes for the data transfer
    An entry in this field is only relevant from release 3.1I onwards.
    Enter a number larger than 0. The maximum number of parallel processes is set by default at 2. The ideal parameter selection depends on the configuration of the application server, which you use for transferring data.
    6. Background job target system
    Enter the name of the application server on which the extraction job is to be processed.
    To determine the name of the application server, choose
    Tools -> Administration -> Monitor -> System monitoring -> Server. The name of the application server is displayed in the column Computer.
    7. Maximum Number of Data Packages in a Delta Request
    With this parameter, you can restrict the number of data packages in a delta request or in the repetition of a delta request.
    Only use this restriction when you expect delta requests with a very high data volume, so that, despite sufficiently large data package sizes, more than 1000 data packages can result in a request.
    With an initial value or when the value is 0, there is no restriction. Only a value larger than 0 leads to a restriction in the number of data packages. For reasons of consistency, this number is not generally exactly adhered to. The actual restriction can, depending on how much the data is compressed in the qRFC queue , deviate from the given limit by up to 100.
    Used to change the Datapacket Size.
    Edited by: Surendra Reddy on Mar 12, 2010 6:27 AM

Maybe you are looking for