General question: XI - older SAP systems?

Hi,
I have been trying to develop a demonstration system using XI 3.0 to link a third party App (file adapter) with an existing R/3 4.6 system (IDOC adapter). But I have run into repeated issues (still stuck at the first hurdle of getting IDOC's imported into Integration Repository) and it seems that maybe I need to do some special configuration and/or add service packs on the R/3 side. Which leads to my question - is this usually the case? Do existing R/3 systems inevitable have to be specially configured to talk to XI?
And if so is there anywhere that lays out in one place what the requirements are for an existing SAP system (in my case R/3 4.6C but my question is also of a general nature) to be able to talk to XI? - I have seen some notes on the subject but seemingly only piecemeal information.
Many thanks for any comments!
best regards,
Chris

Hi Simon,
Many thanks for the reply. The specific problem I am running into is when importing IDOC into Integration Repository. First off I had to get around login issues, (related to uppercase/lowercase) solved with thanks to a genius on this forum, then I ran into this:
com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: The function module "DD_DOMA_GET" not released for 'remote' function calls.
I did find a note which mentioned a fix for this and also recommended that I install service packs but I was just wondering before doing so whether this was a small configuration problem specific to my setup or symptomatic of a wider issue of XI backward compatibility. Hence my original question, I just wanted to get an idea about how often when involved in an XI installation/configuration, there would be a requirement for fiddling with older SAP systems to get them talking to XI.
Cheers,
Chris

Similar Messages

Many Patch/Upgrade Questions/Processes for SAP Systems

Hello, I am trying to wrap my head around the patching/update process in SAP. I am familiar with how to use SPAM and SAINT, but my questions are more about the process as a whole. Here are some of my concerns:
- Do you update the OS or SAP first?
- Do you just apply only OS Service Packs or do you do all security patches as well?
- Should kernel updates be done before or after database patches?
- How do I update the kernel on a cluster?
- Should you go to the latest database patches available or go to a certain level?
- Are some areas more important to update then others?
- How are all of our customizations (1000+ in ERP) handled by the patches?
- What if we implemented an OSS Note that is fixed in a support patch?
- How do we test to ensure we are not doing damage?
- Can you uninstall security patches?
- Is there a way to know what t-codes are affected by the updates?
Just for reference, we are running an ECC 6.0 system on Windows 2003 x64 servers, with a MS SQL 2005 db. Our Prod environment is running in high-availability via MS clustering services. Your input on these questions is appreciated.

Hello Techies,
I am new to SAP and have done course in SAP-BASIS MODULE.
I would like to know the major tasks to be done by basis admin daily,weekly,monthly and how and when to do those tasks???
Please help me out...i am in a desperate need of it..
please mail me on
my email id <removed by moderator>
Thanks & Regards,
Ayaz

General Question about SAP Documentation. Where to find?

Hello,
I am relatively new in the SAP business and so I have some general questions about the SAP Documentation.
Often internet-links like
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/FIBP/FI-AP-AP-PT.pdf
are posted here by group members.
But where do these group members find these documents?
All I can see at help.sap.com is IDES (the model company created by SAP)and the WWW-version of the SAP-Bibliothek.
Were can I find these PDF-Files?
I would appreciate any hint and tip!
Thank you!
Kakue

thats true! i dont know how to find either. Everytime i need something i ask on the forum.
Here's a good link
http://www.easymarketplace.de/online-pdfs.php
Plz reward points if helpfull

Can all SAP System releases be connected to VC?

Hello folks,
our customers would like to know if it is possible to also connect older SAP System Releases like R/3 4.7 to the Visual Composer or even older releases. Are there any connection restrictions concerning the SAP Backend System Release?
Thanks,
Katharna

Hi Katharina,
this is standard connector, which is described here:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/de/21/58feb70e884bc68a474429ac26f448/content.htm">http://help.sap.com/saphelp_nw2004s/helpdata/de/21/58feb70e884bc68a474429ac26f448/content.htm</a>
So it should be possible that you can use your R/3 system with Visual Composer.
Best Regards,
Marcel

SAP GRC Process Control - General Questions

Hi all,
We have the following general questions regarding SAP GRC Process Control:
1) Assume that we have set up 5 different SAP Connectors in Process Control. When you configured a specific rule and control and then, schedule the job for such control, how does the system (SAP Process Control) knows which back-end system needs to be accesed for such control?
2) In which language are the out-of-the box rule steps's script coded? In which different languages can those scripts be coded, what is to say, in which language can we code our own scripts?
3) How is the detailed flow between SAP Process Control and SAP Back-end system?
Many thanks. Regards,
Imanol

null

Another IISPROXY question (multiple SAP systems)

Hi!
We've got a challenge. We have SAP EP (6.0 SP12), visible from outside
(via MS ISA server publishing). Also we have several SAP systems (BW,
ERP2004, Solution Manager), that we want to make available from web.
We installed IIS proxy module on portal server machine. It's working.
I even maneged to publish some test reports and WebGUI of BW server.
But when I try to publish in a simmilar way other system, I fall into
problem.
When you call '/sap/bw/' for example, SAP system after authentication
converts it to something like '/sap(lsdkSDF435ssdgf)/bw'. As far as I
understand between "(" and ")" there is some hash of password or something.
The problem is, that it's true and the same for all SAP systems.
So if I put in iisproxy.xml following strings:
<mapping name="bw">
<source>
     <protocol>http</protocol>
     <prefix>/sap/bw/</prefix>
</source>
<source>
     <protocol>http</protocol>
     <prefix>/sap/bw</prefix>
</source>
<source>
     <protocol>http</protocol>
     <prefix>/sap/public/bc/its/mimes/</prefix>
</source>
<source>
     <protocol>http</protocol>
     <prefix>/sap(</prefix>
</source>
<target>
        <protocol>http</protocol>
     <host>bw-server.ourdomain.local</host>
     <port>8000</port>
</target>
<compress-types>text/html, text/plain</compress-types>
</mapping>
it's working for BW server. We able to see reports and webGUI.
If I try to add following strings for ERP2004 server:
<mapping name="erp">
     <source>
          <protocol>http</protocol>
          <prefix>/erp/sap/bc/gui/sap/</prefix>
          <new-prefix>/sap/bc/gui/sap/</new-prefix>
     </source>
     <source>
          <protocol>http</protocol>
          <prefix>/erp/sap/bc/gui/sap</prefix>
          <new-prefix>/sap/bc/gui/sap</new-prefix>
     </source>
     <source>
          <protocol>http</protocol>
          <prefix>/erp/sap/bw/BEx</prefix>
          <new-prefix>/sap/bw/BEx</new-prefix>
     </source>
     <source>
          <protocol>http</protocol>
          <prefix>/erp/sap/bw/BEx/</prefix>
          <new-prefix>/sap/bw/BEx/</new-prefix>
     </source>
     <source>
          <protocol>http</protocol>
          <prefix>/erp/sap/public/bc/its/mimes/</prefix>
          <new-prefix>/sap/public/bc/its/mimes/</new-prefix>
     </source>
     <source>
          <protocol>http</protocol>
          <prefix>/erp/sap/public/bc/ur/Design2002/</prefix>
          <new-prefix>/sap/public/bc/ur/Design2002/</new-prefix>
     </source>
     <source>
          <protocol>http</protocol>
          <prefix>/erp/sap/bc/public/systemlogin/</prefix>
          <new-prefix>/sap/bc/public/systemlogin/</new-prefix>
     </source>
     <source>
          <protocol>http</protocol>
          <prefix>/sap(</prefix>
     </source>
     <target>
          <protocol>http</protocol>
          <host>erp2004-server.ourdomain.local</host>
          <port>8000</port>
     </target>
<compress-types>text/html, text/plain</compress-types>
</mapping>
and try to open webGUI, it redirects to BW server.
A think that's because double '/sap(' prefixes.
How can we avoid that?
Same situation for SolMan.
In portal's 'System Landscape' setup is:
BW system
ITS
    ITS description: CLIxxxSID
    ITS host name: portal-server.ourdomain.ru (this name in accessible from internet, it's a host where portal and IISPROXY are installed)
    ITS path: /sap/bc/gui/sap/its/webgui
ERP2004 system
ITS
    ITS description: CLIxxxSID
    ITS host name: portal-server.ourdomain.ru
    ITS path: /erp/sap/bc/gui/sap/its/ (I added /erp/ trying to distinguish request to ERP2004 server), without it it's also not working)
In intranet (if we do not use IISPROXY) everything is working. Of course with other system definitions in System Landscape.
Do I need to provide more details? Or my question is clear?
Thanks in advance for help and support!
Regards,
DK
P.S. Actually I opened an OSS message on this topic (with "high" priority), but no SAP activities since September, 6th :o(

Hi Jayesh!
Seems it's not working :o( And worst thing, that I do not know why :o(
What i've done.
1) Created an alias '/erp/sap/', that points to '/default_host/sap/bc/gui/sap/its/webgui'.
2) In System Landscape edited system definition (of an ERP2004 system), so that ITS path is now '/erp/sap/' and ITS host 'ourportal.ourdomain.ru'.
3) Created an 'SAP transaction iView' that should launch SU01 transaction in ERP2004 system.
Now when I try to open it from page, portal tries to connect me to our BW server.
Seems that alias are working in some other way :o(
Here's what I can see in IISPROXY log:
11:57:29 Filter J2EE --> GET /erp/sap/
11:57:29   7616 Proxy    GET http://erp2004.ourdomain.ru:8000/erp/sap/
11:57:29   7616 Proxy    HTTP/1.1 200 OK | queued for 0.000 sec, processed in 0.078 sec.
11:57:29   7616 Proxy    | GET http://erp2004.ourdomain.ru:8000/erp/sap/ | HTTP/1.1 200 OK | 0.000 | 0.078
11:59:41 Filter J2EE --> GET /sap(dslkknvDSAFSADVFDSVaslkdv)/bc/gui/sap/its/webgui?okcode=/nSU01&DisconnectOnClose=0&sap-client=200&sap-language=en&sap-accessibility=
11:59:41   6952 Proxy    GET http://bw.ourdomain.local:8000/sap(dslkknvDSAFSADVFDSVaslkdv)/bc/gui/sap/its/webgui
So it's still tries to open '/sap(dslkknvDSAFSADVFDSVaslkdv)/bc/gui/sap/its/webgui' instead of /erp/sap(
dslkknvDSAFSADVFDSVaslkdv)/
Thanks for help and support!
Regards,
DK

Crystal report and SAP system question

Hi,
I try to report off the SAP system using crystal reports without installation of the BOE server. But with very few knowledge of the SAP system, I am not clear of how and what to do. The following is what I have done:
1. From the client machine, I open the crystal report 2008
2. click "SAP" button and then click "Create New Report from a Query"
3. Select the system and enter the login user name/ password information
4. A dialog "Select Query for your Crystal Report" displayed.
    But under "Favorites", no entry found
    Under "Roles", no entry found
    Under infoAreas, there is a "Technical content" on top level and "Exchange Rate Type" is under it. I select this exchange rate type in the report, but it is an empty table.
If I use the same user name/ password to log on the SAPGUI, I am able to see lots of data.
Does anyone know what are the appropriate configuration steps to make the tables/views in the SAP system visible in the crystal reports? Could you please give me the details? Any help is appreciated.
Thanks,
Vicky

Hi,
are you trying to report on top of a BW query (mentioned in step 1 and 2) or you trying to create a report on top of tables (mentioned further down).
Ingo

Beginner Question: How to disable Sound in Mini-SAP-System

Hi.
I am at the very beginning with ABAP and installed the Mini-SAP-System.
The sound effects make me crazy, how can you turn them off? I did not find any information in the help of sap.
Anyway, does anyone not turn off these crazy sound effects ?! How can you work concentrated with them?
Thank you a lot...

Ok, sorry, i should have posted it in another forum i see.
>
bala wrote:
> In the top right in any SAP screen (Customize local Layout). Go through the tabs and you'll see it in
> the area where you set messages E.g. 'beep at message'
>
> Confirm, if solved.
Ok, i am within local layout, then options. The first tab contains "messages" with the options:
beep at message
dialog windows at success message
and two more.
None of these is activated. So I wonder why I get the sounds nevertheless each time i make a click within the mini SAP system ?!
And I do not find any other sound options anywhere at the "local layout" configuration...
Edited by: Kai Waehner on Jan 13, 2009 10:58 AM

Could anybody advise the general procedure for SAP system migration?

I may have chance to be involved into a SAP system migration. Generlly speaking, there are several SAP instances will be migrated into 1 box.The existing instances are 4.6C, and the target instance is ECC6.
Could anybody provide me some reference material for SAP system migration? or Is there any tools or software can facilitate the migration?
Thank you so much!
null

We are currently running and upgrade from 46C to ECC6 and I have found the following very usefull:
<a href="https://websmp108.sap-ag.de/upgrade-erp">Upgrade Guides</a>
SAP Notes:
Note 825146 - Add. info. on upgrading to SAP NW04s (SR1, SR2) MSSQL
Note 913971 - Add. info. on upgrading to SAP ERP Central Component 6.0 SR
Note 813658 - Repairs for upgrades to products based on SAP NW 2004s AS
Hope this helps!!
Phil
Message was edited by:
Phil Wade

SAP GENERAL QUESTION

HI,
CAN U PLEASE ABBREVIATE THE TERM 'SE' IN TRANSACTION CODE ?
EX: SE16...
WHAT IS THE TERM 'SE'?
THANKS,
KAMAL
Moderator message: please search for information, do not post in all upper case, use meaningful titles, read the rules of engagement before posting again.
Edited by: Thomas Zloch on Jan 17, 2012

Hi,
It is possible to do either. Customers run their own data centres to host their systems, or SAP provide a service (through SAP Hosting) to run the SAP system for you. It is also possible to hire other third parties (hp, IBM etc) who will host SAP systems for you.
Regards,
Nick

SAP CM25 which profile to use and why and some general questions

Hi there,
I have a few general questions, if you may share your thoughts on this.
In a manufacturing environment, is CM25 more used to finite schedule the work centers or labor or both ?
Is it a good idea to even finite schedule the planned orders or just production orders ? We want to create production orders 1 week ahead of the production schedule and planned orders gets created 3-4 weeks earlier than production order gets created.
The graphical tool seems to be slow sometimes when dispatching and doing some actions on the screen, has any one have any say on this. Should we need to have better computers on the floor for this to work ?
I have been trying my solutions using CM25 and not CM21 or CM27 using the profile SAPSFCG005, is there any other profile that I need to consider and other transactions to consider like CM21 or CM27 for certain purposes?
Thank you

Hello
In a manufacturing environment, is CM25 more used to finite schedule the work centers or labor or both ?
It can be used for both depend upon bottle neck resource whether machine or labour.
Is it a good idea to even finite schedule the planned orders or just production orders ? We want to create production orders 1 week ahead of the production schedule and planned orders gets created 3-4 weeks earlier than production order gets created.
Better it should be finite planning for planned order also you can use MRP with lead time scheduling.
The graphical tool seems to be slow sometimes when dispatching and doing some actions on the screen, has any one have any say on this. Should we need to have better computers on the floor for this to work ?
It depends upon the data load and selection,
Restrict the number of objects to be displayed, for example, select only a small number of work-centers/orders.
Customize the time profile (transaction OPD2) such that the database read period, the planning period and the evaluation period are as small as possible. As a result, fewer objects are read and displayed.
Refer KBA 2038780 - Tips for performance improvement on Capacity Leveling
If you want to process more orders, check whether a batch planning (planning in the background on transaction CM40) is possible.
I have been trying my solutions using CM25 and not CM21 or CM27 using the profile SAPSFCG005, is there any other profile that I need to consider and other transactions to consider like CM21 or CM27 for certain purposes?
It depends upon your requirements which transaction to use and which profile. You can customize your own profile also.
Best Regards,
R.Brahmankar

Questions on the SAP payment program

Hi everyone,
Here are general questions the SAP payment program. Even partial answers would be greatly appreciated. Thanks in advance!
Questions:
What are the type of accounts involved in a payment transaction? In which case a customer account could be involved?
What could "payment proposal run" mean and imply?
What could be done as "editing a proposal run"?
In the "print payment media" step, what does DME stands for?
And in general, what are the diffenrences between a posting and an FI document?
Is the payment run launched automatically?
Thanks again
SB

What are the type of accounts involved in a payment transaction? In which case a customer account could be involved?
You will make the payments to vendors and customers accounts. Customer accounts may involve where you would like to make payment for the advance that you have received from customers.
What could "payment proposal run" mean and imply?
Payment proposal is nothing but SAP will give you a simulation showing what are the invoices going to be paid, what are the invoice not going to be paid (exception) due to various reasons.
What could be done as "editing a proposal run"?
In Editing the Payament proposal, you can block a invoice, which you would not like to make the payment. You have to create the payment block specially for the purpose of payment proposal.
In the "print payment media" step, what does DME stands for?
DME - Data Medium Exchange
And in general, what are the diffenrences between a posting and an FI document?
Posting is posting a document into the system.
FI document is a document having debit and credit totalled. To post a document both and debit and credit must be tallied.
Is the payment run launched automatically?
There is no automatic launching of Automatic Payment Program. You can schedule the job in background, but I would not recommend this. I would recommend the user to enter the parameters, run proposal, execute payment run and print the media.
Regards,
Ravi

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

'BAPI_DOCUMENT_CREATE2': store attachment using 'SAP-SYSTEM'

while i am checkin a document (attachment) using storage category KPRO ,the document is getting stored but when i use SAP-SYSTEM the Document is not getting stored. How can I get it stored using 'SAP-SYSTEM'
Following is the code;
DATA:
lv_docnum TYPE bapi_doc_aux-docnumber,
lw_docdata TYPE bapi_doc_draw2,
lw_return TYPE bapiret2,
lw_dsp TYPE bapi_doc_drat,
lw_objlink TYPE bapi_doc_drad,
lw_docfile TYPE bapi_doc_files2,
lt_dsp TYPE STANDARD TABLE OF bapi_doc_drat,
lt_objlink TYPE STANDARD TABLE OF bapi_doc_drad,
lt_docfile TYPE STANDARD TABLE OF bapi_doc_files2.
START-OF-SELECTION.
*CALL 'SAPCORE' ID 'ID' FIELD 'VERSION'
ID 'TABLE' FIELD kernel_version-sys*.
*READ TABLE kernel_version INDEX 11.
*w_hostname = kernel_version-data.
CLEAR lw_docdata.
lw_docdata-documenttype = 'ZAP'.
lw_docdata-documentversion = 'A0'.
lw_docdata-documentpart = '000'.
lw_docdata-laboratory = '001'.
CLEAR lw_dsp.
lw_dsp-description = 'Test created by xyz'.
lw_dsp-language = 'E'.
APPEND lw_dsp TO lt_dsp.
lw_docfile-docfile = 'C:\test.pdf'.
   lw_docfile-docpath = 'C:\test.pdf'.
LW_DOCFILE-ORIGINALTYPE = '1'.
lw_docfile-storagecategory = 'SAP-SYSTEM'.
lw_docfile-storagecategory = 'DMS_C1_ST'.
lw_docfile-wsapplication = 'PDF'.
lw_docfile-language = 'E'.
lw_docfile-checkedin = ' '.
lw_docfile-checkedin = 'X'.
lw_docfile-active_version = 'X'.
APPEND lw_docfile TO lt_docfile.
CLEAR lw_objlink.
lw_objlink-objecttype = 'VBAP'.
lw_objlink-objectkey = '0040011233000010'.
lw_objlink-documentdirection = 'X'.
APPEND lw_objlink TO lt_objlink.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
    EXPORTING
      documentdata         = lw_docdata
pf_ftp_dest = 'SAPFTPA'
pf_http_dest = 'SAPHTTPA'
    IMPORTING
      documentnumber       = lv_docnum
      return               = lw_return
    TABLES
      documentdescriptions = lt_dsp
      objectlinks          = lt_objlink
      documentfiles        = lt_docfile.
IF lw_return-type CA 'EA'.
    CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    MESSAGE ID lw_return-id
    TYPE lw_return-type
    NUMBER lw_return-number.
ELSE.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = 'X'.
    CLEAR lw_return.
    CALL FUNCTION 'BAPI_DOCUMENT_CHECKIN2'
      EXPORTING
        documenttype    = 'ZAP'
        documentnumber = lv_docnum
        documentpart    = '000'
        documentversion = 'A0'
      IMPORTING
        return          = lw_return
      TABLES
        documentfiles   = lt_docfile.
    IF lw_return-type CA 'EA'.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      MESSAGE ID lw_return-id
      TYPE lw_return-type
      NUMBER lw_return-number.
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
    WRITE: / 'document number = ', lv_docnum.
    ENDIF.
ENDIF.

Hi,
based on the posted coding I think that the reason for this behavior is that the used document type has set the flag 'Use KPRO' in transaction DC10. Because the storage category 'SAP-SYSTEM' is not a KPRO storage category like DMS_C1_ST. So if this flag is set in the customer then only originals checked in to a KPRO storage category are displayed. Without this flag the originals in "older" storage categories are displayed (e.g. SAP-SYSTEM, archive,...).
Regarding the limitation of 2 originals per document info record, I can inform you that this is a standard restriction of you do not
check in your originals to a KPRO. With the KPRO storage there is no such limitation.
Generally I'm asking myself why you are using the BAPI_DOCUMENT_CREATE2 and then also the CHECKIN BAPI. Because you can enter the original data also at the CREATE2 BAPI. If you want to checkin files to the KPRO then the filedata has to be
handed over in table DOCUMENTFILES. If you want to check in originals to SAP-SYSTEM then the data has to be entered in table DOCUMENTDATA. For further information please see SAP note 766277 which has a complete BAPI documentation added in its attachment area.
Best regards,
Christoph

App.server load balancing for SAP System with 1 PS

Hi,
In SAP CPS 7.0 (Build M26.12) I have a SAP system with Central Instance + 10 App.servers, but all instances are managed by 1 ProcessServer.
After activating the "App.server load balancing" setting in SAP system definition the application servers are becoming visible in CPS with their load factors (number of BGD wp's on app.servers) and load numbers (number of active jobs on app.servers).
This is so far fine, but the additional functionality is not working as I would expect, I have issues with 2 functionalities:
1. Based on documentation after activating also the XAL connection the CPS should submit the job on app.server with best performance based on XAL monitoring data filling the TARGET_SERVER parameter.
This functionality is not working for me at all
2. A useful functionality after activating the "App.server load balancing" setting is that the ProcessServer is going to "Overloaded" status when all BGD wp's of SAP system are occupied, thus restricting submitting new jobs during overload situation. But I had an issue also with this functionality, after SAP system recovery from overload situation, the CPS still remained in Overload status (so no new jobs were submitted).
As a workaround I had increased the treshold values for loads on all app.servers for this SAP system, what was fine for several days, but after a while I believe this was a reason of unexpected performance issues in CPS, therefore I have deactivated the 'App.server load balancing" setting at all for this ProcessServer.
I would appreciate your feedbacks with this functionality.
Thanks and Regards,
Ernest Liczki

Hi Preetish,
This connect string option is to loadbalance RFC connections. These are balanced upon login, once you are connected to a particular application server (AS) you stay on that server until you reconnect.
Since CPS uses multiple RFC connections, this will result in the connections being distributed over the available AS resources which is fine as long as they are generally evenly loaded. If you have certain AS hosts that are continuosly more loaded than the rest, then you probably don't want the CPS RFC connections to end up on these servers.
The original question is about loadbalancing of batch jobs over the available AS resources, and this is done independent of the RFC connection load balancing. Even if all CPS RFC connections are pinned to the DB/CI host, you can still loadbalance jobs over the available SAP AS hosts, either by using SAPs builtin balancing, or the CPS algorithm by activating the checkbox as indicated in the first entry in this thread.
Finally, to reply to Ernest's question: I believe there are some fixes on the app load balancing in the latest release, M26.17 should be available on the SWDC now.
Regards,
Anton.
Edited by: Anton Goselink on May 29, 2009 9:06 PM

General question: XI - older SAP systems?

Similar Messages

Maybe you are looking for