ARE-1 through SAP Systems

Hi,Experts
Our Client regular export to our customer and now present they
will prepare ARE-1 in Excel in manual..
As per their requirement .
1)They prepare 5 export Invoice and ARE-1 prepare common for One
container.(maximum 8 Items)
2) Net Weight & Gross weight of all invoices is common in ARE-1
3) Marks & Nos of all inoices should by common in ARE-1
4) UT-1 bond reference should mention on both side( i.e.front &
back
side should be print)
5) If export in Rebate excise duty debit entry of all 5 invoices
should be print on invoice.
6) Container No/Excise Seal & Line seal also mention in ARE-1.
7) All five Excise & Export Invoice reference shown in ARE-1.
Your help is highly appreciated.
Thanks
Babita

Dear J.P Sir,
As per retro billing configuration
we maintain condition record based on Sales org./Distr. Chl/Customer/Material/Pur. order/PO item. but when change price in condition record .after that run retro billing .system not show the value of current net value it show only item net value and retro billing value and billed quantity.
if i set one more maintain record based on customer material then its comes current net value,but client dont want two times maintain condition record. so,suggest me how to do.
Thanks

Similar Messages

Customer agreement with organization through SAP System

Dear Gurus,
I have got a requirement from my client.
there is an agreement between customer and company that they will do business for the period of one year. After one year, the customer needs to renew their agreement with company for the next year to keep on the business process. This agreement is a manual process.
Now the requirement is need to full-fill from SAP system. They require search criteria also to know the expiration of agreement of customer with company before a month.
Can anyone help me on that, kindly suggest how can i achieve this in SAP?
Rgds

Hi,
If there is no sales involved..just pick up any cond type with the required fields like customer code etc..it'll have validity periods as well.. and you can always view them using VK13--condition info.
If there is no sales with that customer, the cond record wont get picked up..
Alternatively, create a rebate agreement with customer and validity periods and etc..do not maintain any rebate cond records.
This should also work for your scenario though am curious to know what business if not sales?
Regards
Raghu.

What are system variants and where they are stored in SAP?

HI EXPERTS,
        i want to know the use of system variants . when we create the variants in reports. where these system variants are stored in sap system?
thanks in advance.
vikas

The variant are stored in tables
- VARI     ABAP/4: Variant storage (similar to INDX)
- VARID     Variant directory
- VARIT     Variant texts
You can access to these through function modules of group SVAR Variant maintenance (most of them begin with [RS_VARIANT_|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=rs_variant_*+&adv=false&sortby=cm_rnd_rankvalue])
Look also at [Creating Variants (SAP documentation)|http://help.sap.com/saphelp_webas630/helpdata/en/c0/980389e58611d194cc00a0c94260a5/frameset.htm] or [search Sdn for SVAR|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=svar&adv=false&sortby=cm_rnd_rankvalue]
System variants (CUS&, SAP&) are not editable when Client has status 'not modifiable' (as it is in productions system) also when edited in development system they are automatically transported.
Regards

SAP System is not the original system of the object being edited

Hi All,
We recently built a new system which is Copy of another system.We decomission our old system.Now when ABAPer is trying to edit Z/Y programs in se38 they are getting message "SAP System is not the original system of the object being edited".We already completed all post process after system copy.Client is open and status in Golbal modifiable in se06.
How we can resolve this situation.

Hello Guys,
Thks for your input.
@Vinod,
We rebuild new development system from the exsisting devlopment system and scrap old one.And yes thats true that new system is not the original system where object was created,its a replica of old dev to nev dev with SID change.
@Arjun,
I already check TADIR table and and its pointing to new SID.
@Ashok,
As i said earlier,post intallation is already completed.
Its a problem for developer who's getting some different format of screen when they editing development object ,like, when we perform manaul corretion in abap code through snote.They can see buttons to insert code line,delete line.
Thx,Nilesh

Sap systems connection

I can log on two sap systems whick at different place,one is through the routers and the other is not.
My question is How can I connect them by TCODE SM59.

Hello Plane,
As you are connecting two SAP Systems at different location using SM59, it becomes R/3 Connection of type 3.
So, go to the transaction SM59 and follow the following details
->Select R/3 connection and click on Create
->Give the connection type as 3 and give the description
->In the Technical Settings Tab,
   -->> Give the Taget Host with the Ip address of the target SAP System
   -->> Also, fill the System Number
->In the Logon/Security Tab,
   -->> Give the Language
   -->> Client Number of the target system
   -->> Username and Password of the target system.
Save it and Click on Test Connection
Hope this is helpful

Restrictions from SAP Systems to the emails adding

Gentlemen,
Regarding SMTP Email Configuration, I already applied SAP Note u201C455140u201D and every thing its working fine, I can send email through SAP Systems no problem,
My question is,
There are no restrictions from SAP Systems to the emails as I can put any Emil in E-mail address in user ID properties and I can send with it without any problem and this is not logical,
Please advice.
Regards,
Ahmed Saber

Hi NALLAM GUNA RAN,
First, thanks for fast reply
Please can you explain in more details what you mean of XI/PI box,
And whatu2019s the solution of this situation as itu2019s not accepted from customers.
Regards,
Ahmed Saber

Need of XI to send an XML from one SAP system to another SAP system

Dear colleagues,
I work in the SRM solution.
In SRM there is a Purchaser and Supplier scenario called Supplier Self Services.
The Purchaser creates a Purchase order and sends it to the supplier in form of an XML file.
The purchaser system and supplier system are the same SAP system but different clients.
Example: Purchaser client is 300 and Supplier client is 330 and both of them are on the same system.
I have a very basic question.
Currently we have the XI system which acts as an interface to send the Purchaser PO XML to the Supplier as XML.
a)My question is in case the XML structure is identical across both the clients, then what is the need of XI system?
b) Is it not possible to send XML from one client to another without an XI system? there si no need of any message mapping required since I am expecting the same XML structure in both clients.
Please clarify the need of XI system in the following scenario. Is it not possible without XI?
Many thanks.
Best regards,
Srivatsa

Hi Srivatsa,
YOu can send the XML message from one sap system to another sap system even without an XI system in between.
But the use of SAP XI (Or any other middleware) is recommended because, it gives you the following advantages.
1) Better monitoring and alerting mechanism. XI provides you robust set of tools that let you monitor the status of the messages that are exchanged.
2) Direct communication between systems is referred to as Point to Point communication, which has its own disadvantages as against Hub and SPoke model (Message exchange using XI).
3) Message delivery is guaranteed if you have XI in between.
If the target system is down, the sender sap system will not try multiple times to post the message.
But if you use XI, it can be configured to send the message multiple times, till it succeeds.
Regards,
Ravi Kanth Talagana

Problem accessing clicksoft webservice in SAP System

Hi All,
We are currently integrating SAP system with Clicksoft. For that, we have received WSDL file from Clicksoft and we are trying to create consumer proxy in SAP system.
But, getting error " Attribute "Transport" in <SOAPbind:binding> has incorrect value.
Regards,
Sagarika

Hi ,
As this forum is for SharePoint and this question is about third party, I changed its type to discussion.
Thanks,
Wendy Li
TechNet Community Support

Inbound idoc failing to reach SAP system.

Hi All,
We are upgrading our SAP system from release 700 to 730. Post upgrade we have identified that idocs which are supposed to reach SAP as inbound are failing in Biz Talk with below message.
Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDT37003GRP IDOCTYP: SHPMNT03 Release: 700 CIMTYP: . Ensure that your message xml validates against the operation schema.
This happening for only one inbound idoc which is using SHPMNT03 idoc.Whereas other inbound idoc which is using /AFS/ORDERS05 idoc is reaching SAP without any issues. I am bit confused why this is happening for idoc SHPMNT03.
Please let me know your thoughts.
Thanks,
Gowrinath.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Parallel How many times user can login to the SAP system through ITS

Hello all
We are using the ITS ---620 and following 46D R/3 system
R/3 system details:
Kernal :
kernel release :46D
O/S :SunOS 5.8 Generic_108528-05 sun4us
We would like to now, At a time How many times user can login to the SAP system through ITS
Kindly letus know if any one have idea about parameter which can restrict the end users to u201CNu201D times/ sessions.
Transaction SITSPMON/SMICM are not working in R/3 system as it is 46D.
We found that parameter u201Clogin/disable_multi_gui_loginu201D works with SAPgui logons.
System logons using the Internet Transaction Server (ITS) or Remote Function Call (RFC) are not affected by this Parameter u201Clogin/disable_multi_gui_loginu201D
I need similar parameter u201Clogin/disable_multi_gui_loginu201D for the ITS users.
Thanks

I have searched all docs and notes.
Everytime the answer is PArameter for multi_gui_logonis not applicable for SAP Gui for HTML ( Browser )
The functionality does not exist for SAP Gui for HTML.
Regards,

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

HOW TO SEND THE REPORTS AND THROUGH XI TO NON -SAP SYSTEM

Hi Experts,
I want to know how to send the reports and smartform through xi to another system. All the post blogs are just explaning only about the FILE-TO-FILE, FILE-TO-IDOCS scenarios only.

Hi,
XI is the middleware that to be used to transfer the data between various systems and even you could design the Business Processes with it.
In R/3 the smartforms, are generally converted to PDF and then have to send it across to Non SAP systems. Similarly you can convert the smartforms to pdf format and keep it on application server. XI will pick up that pdf and will send it to Non SAP system either as mail or as an attachments.
ABAP reports are normally used to re-present the data. If you need to transfer this data across the Non SAP systems then you have the IDOCs to be generated, RFC or ABAP Proxy to integrate this data with Non SAP system.
XI is not restricted only upto file to file or file to IDOC scenarios. It have enormous capabilities to involve various Business Processes as well integrate various SAP or Non SAP systems.
If need anymore specific details, please let us know.
Thanks
Swarup

Unable to send mails to outlook from sap system through workflow

Hi ,
Iam unable to send mails to outlook from sap system through work flow .Actually we r able to send mails from sap inbox to outlook successfully.But when trying with workflow we r not able to send.Please guide me that is there any configurations required from BASIS side for work flow.Actually we configured everything like default domain .
Please find the errors belows that traced from sost t code
02/13/2012     17:50:12     0380 MIME_MESSAGE_GENERATE     G     Error when generating MIME flow
02/13/2012     17:50:12     0382 MIME_MESSAGE_GENERATE     G     Required 'From' header is initial
02/13/2012     17:50:12     0167 SO_OBJECT_MIME_GET     G     Error during MIME Generation
02/13/2012     17:50:12     0777 UPDATE_SOSC     G     Cannot process message in SAP System
Regards
RAGHAVENADAR

Hello,
Actually i checked the mail ID for WF-BATCH using su01 .But i didnt find any mail ID for WF-BATCH then i added the email address of the user.Then we tried sending mail it was successfull.
But later i removed the email address what i entered in WF-BATCH user .Even after removing the email address also iam able to send the mails through workflow.
So iam confused whether it needs an mail address or not.But now we are able to send a mail to outlook through work flow but not able to send mails to GMAILor yahoo.For that we need to do any settings.
ABAPer is sending mails through work flow.
Regards
RAGHAVENDAR M

VallueMapping update through HTTP from SAP system

Good day everyone,
For two weeks, I have been trying to send xml data from SAP to SAP PI through HTTP. The purpose of this interface is to update the Value Mapping entries in PI from SAP. I know, most of you might tell me to use ABAP proxies to make things more simple and easier. The reason why I did not use ABAP Proxy is because the SAP and SAP PI systems I'm using have different versions. I have SAP Netweaver 7.1 for my PI system and ECC 6.0 for my SAP. I believe it wouldn't be possible to use ABAP/JAVA proxies if the two systems are of different versions.
Here is what I have so far. I created a program to send an HTTP request using an RFC Destination. I used my own UserName and Password in the logon details in the RFC Destination. I used service adapter_plain. Here is the complete URL: http://<host>:<port>/sap/xi/adapter_plain... . I created the necessary objects in Integration Directory and the HTTP sender program. Below, you will see a sample of my payload and the error message I got. Can anyone help me how I could fix this error?
Payload:
<?xml version="1.0"?>
<ns1:ValueMappingReplication xmlns:ns1="http://sap.com/xi/XI/System"
xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance">
<Item>
<Operation>Insert</Operation>
<GroupID>z80c0f608a1d11df928700ffb81a5a80</GroupID>
<Context>http://sap.com/xi/XI</Context>
<Identifier scheme="Blue"
agency="Yellow">GREEN</Identifier>
</Item>
</ns1:ValueMappingReplication>
Error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401 </SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:Stack></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Kind Regards,
Chris C.

> Mapping entries in PI from SAP. I know, most of you might tell me to use ABAP proxies to make things more simple and easier. The reason why I did not use ABAP Proxy is because the SAP and SAP PI systems I'm using have different versions. I have SAP Netweaver 7.1 for my PI system and ECC 6.0 for my SAP. I believe it wouldn't be possible to use ABAP/JAVA proxies if the two systems are of different versions.
Of course this works.
I use APAB proxies with SAP R/3 4.7 to send value mapping data to PI 7.1
Copy the standard value mapping outbound interfaces to your own SWVC and genearate ABAP proxies for it.

Facing Problem In Accessing SAP System through Eclipse ABAP Tool

Hi All,
I am willing to learn SAP ABAP.
I installed SAP GUI 7.30 for windows and Eclipse ABAP Tool.
I also connected to E66 [dkmgd37] System through Consolut but
Whenever i am trying to access SAP System from eclipse ABAP project, it is showing you are not authorized to access this system for ABAP Development.
Could anyone plz help me out. I am also attaching the image of SYSTEM CONNECTION PARAMETERS for E66 System(For Reference).
Thanks & Regards,
Priyanshu

Hi Priyanshu,
To create development objects in SAP , you must have developer access key . Do you have developer access key ? If yes then not have enough roles to create the objects.
To check which authorization object , after getting the error run transaction SU53. Contact the authorization team who created the ID to provide developer roles
Thanks & Regards,
Arun

ARE-1 through SAP Systems

Similar Messages

Maybe you are looking for