Question from a System Integrator

Hi I work for a bank and we have lots of corp. client using SAP as ERM, we provide PCard interfaces(flatfiles extracts) to these companies so they can import these files to their SAP and consolidate their card transactions/generates report etc. from within SAP.
Every company that I have worked for has asked for a different type of customized file, I was wondering does SAP has a standard interface for such integrations so it can make the life easier for this puropose.
Thanks and Regards

Hi Reza,
This sounds like a job for SAP's integration platform, SAP NetWeaver Exchange Infrastructure (XI/PI)!
Learn what you can from the following area:
https://www.sdn.sap.com/irj/sdn/developerareas/xi
What you will need to do is send your PCard flatfile extracts to SAP XI/PI, which is the native integration platform to SAP applications. Beforehand, you will create/configure the SAP XI content which contains the interfaces, mapping rules, transformation, routing rules, etc. Once SAP XI receives your PCard flatfile, your SAP XI content will determine where it needs to go, what format it needs to transform to (e.g. SAP IDoc, SOAP, EDI, etc.), and send it to the respective SAP or non-SAP application. For every new company that you encounter, you will only (hopefully) have to change a few of the exisiting mappings to the new custom format they require. Thus, you can reuse and build upon existing work.
For certification wise, you will choose option 2:
http://www.sdn.sap.com/irj/sdn?rid=/webcontent/uuid/ab919ce1-0601-0010-4384-f25a892e0dea [original link is broken]
Let me know if this helps!
John Ta

Similar Messages

Questions from Linux System Admin on storage

Version Info
+++++++++++
Grid Infrstructure: 11.2.0.3
Platform : Oracle Enterprise Linux 6.3
++++++++++++
We are a big AIX, Solaris shop ! After some meetings with the Oracle Sales guys, our managers have decided to move some of our RAC DBs to Oracle Linux.
Our Linux Admins (RHEL ) never configured machines for RAC before. They have only configured machines for App Servers before.
For the shared LUNs meant for ASM Diskgroups they have asked me how I want to have the LUNs to be ? Physical Volume, Logical Volume .. etc. They spoke about things like pvcreate, vgcreate.. etc.
Any idea how should the storage LUNs have to be presented to Linux RAC Nodes ?

james_p wrote:
Thank you. I have 2 more questions
Question1.
Should it be extended partition or Primary partition ? Should I choose 'e' or 'p' for below ?
# fdisk /dev/sdb
Command action
e extended
p primary partition (1-4)
Use primary partition
>
Question2.
What should be the partition type ? What should I choose from the list below
Command (m for help): t
Selected partition 1
Hex code (type L to list codes): l
0 Empty 1e Hidden W95 FAT1 80 Old Minix bf Solaris
1 FAT12 24 NEC DOS 81 Minix / old Lin c1 DRDOS/sec (FAT-
2 XENIX root 39 Plan 9 82 Linux swap / So c4 DRDOS/sec (FAT-
3 XENIX usr 3c PartitionMagic 83 Linux c6 DRDOS/sec (FAT-
4 FAT16 <32M 40 Venix 80286 84 OS/2 hidden C: c7 Syrinx
5 Extended 41 PPC PReP Boot 85 Linux extended da Non-FS data
6 FAT16 42 SFS 86 NTFS volume set db CP/M / CTOS / .
7 HPFS/NTFS 4d QNX4.x 87 NTFS volume set de Dell Utility
8 AIX 4e QNX4.x 2nd part 88 Linux plaintext df BootIt
9 AIX bootable 4f QNX4.x 3rd part 8e Linux LVM e1 DOS access
a OS/2 Boot Manag 50 OnTrack DM 93 Amoeba e3 DOS R/O
b W95 FAT32 51 OnTrack DM6 Aux 94 Amoeba BBT e4 SpeedStor
c W95 FAT32 (LBA) 52 CP/M 9f BSD/OS eb BeOS fs
e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi ee EFI GPT
f W95 Ext'd (LBA) 54 OnTrackDM6 a5 FreeBSD ef EFI (FAT-12/16/
10 OPUS 55 EZ-Drive a6 OpenBSD f0 Linux/PA-RISC b
11 Hidden FAT12 56 Golden Bow a7 NeXTSTEP f1 SpeedStor
12 Compaq diagnost 5c Priam Edisk a8 Darwin UFS f4 SpeedStor
14 Hidden FAT16 3 61 SpeedStor a9 NetBSD f2 DOS secondary
16 Hidden FAT16 63 GNU HURD or Sys ab Darwin boot fb VMware VMFS
17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fc VMware VMKCORE
18 AST SmartSleep 65 Novell Netware b8 BSDI swap fd Linux raid auto
1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid fe LANstep
1c Hidden W95 FAT3 75 PC/IX be Solaris boot ff BBT
Hex code (type L to list codes): 82
Changed system type of partition 1 to 82 (Linux swap / Solaris)
Leave to default.
You will need this:
http://docs.oracle.com/cd/E11882_01/install.112/e22489/storage.htm#CDEBFDEH

Why can't I post a question from my new system?

Hello All:
I was just trying to post a question from my new mbp but it wouldn't allow me to do anything. It continually gave me a message highlighted in 'red' that i was;t allowed to modify or post anything. I've been asking questions for quite a while and have never seen this. I also happen to have my older bmp, also logged onto the 'Apple Discussions' site, open beside me. Can anyone explain this to me please? BTW, my new system obviously has Yosemite on it while my older bmp has Lion. Thanks in advance, to all those who respond.
Regards,
Ciaochiao

ChitlinsCC, I'm adding your reloaders to my article on how to make using ASC easier.
Here is my ASC work flow...
1) I login.
2) Block the automatic 30 minute logout.
     Unless you do something every thirty minutes you get logged out. The forum software waits to tell you this as long as it can to keep you in suspense ;-) . Filling out a reply is the exception to the thirty minute window.
        Start an auto reloader.
Safari = SafariTabReloader
Firefox = ReloadEvery: "Reload web pages automatically"
Others = Reloaders | Cerberus - Support Center
You need to pick a page that will reload over time without stalling out. It's ASC. I've found my profile display the best to use. I get my Profile page after some logins. It's ASC. Change rccharles to your apple id.
https://discussions.apple.com/people/rccharles?view=discussions
Reply technique
Open a new browser window. Pick some discussion. Open a reply window. As long as this reply window is open, you will stay logged in. The 30 minute times is reset as needed by the ASC software.
3) I open another window to do my normal ASC browsing.
4) I have a FireFox bookmark to goto the discussions that I have participated in. I've modified it to add on the content stuff.
         turingtest2 recommends. Change rccharles to your apple id:
https://discussions.apple.com/people/rccharles/content?filterID=participated~obj ecttype~objecttype%5Bthread%5D
5) Use turingtest2's generated links with the /content suffix as browser bookmark to the ASC discussions:
Site map of Communities and Categories
https://discussions.apple.com/docs/DOC-2463
6) Adjust the ASC web page layout.
For FireFox
I run with Hiroto's modification to user content. This is the only way these forums are readable for me. How to adjust the format and layout of ASC Web Pages:
https://discussions.apple.com/docs/DOC-7501
For Safari
"ASCPowerTools is a Safari Extension designed to give more control"
http://www.etresoft.com/ascpowertools
7) Read and answer my old posts. I kind of memorize the time I last posted. ( It's way bad that apple eliminated the last poster to a thread. )
8) I use tabbed browsering. From a list of discussions, hold down the command key then click on the link. You get two tabs this way. The original window will keep where you have been.

Use of Discovery System :question from a vendors perspective

Hi all
I have a question regarding Discovery System(DS) from a vendors perspective.
what can client actually do with the DS as soon as they buy it, beside using the demo scenario?
Going through the demo if the client decides to use Discovery system, What sorts of works are necessary for fitting the DS and replacing the existing system? Lets us suppose that the client is previously using SAP software(R/3), in this case how he can start using the DS?
Does he have to set a project, the size that of while implementing R/3, and use a great deal of resource for doing the fitting work, the add-ons and testing?
I am just curious about the approximate cost of the implementation and how the client can be persuaded for the ROI on DS.
I am really looking forward to hearing from you.
thanks in advance
sudeep

Hi Sudeep,
to your questions:
- planning migrations
You can evaluate what you will get (technically and functionally) after a migration by looking at the Discovery System already in advance. Customers use that option to shortlist and prioritize new stuff to implement after a migration.
- evaluate compliance tools
Almost the same as above with the difference in the tools/topics. Check out on the DS what you will get in the area of compliance tools without the need for a dedicated project/system.
- simulate business processes
Use the modeling and composition tools to develop new variations of business processes to better suite the needs of your business.
POC's = proof of concepts
Hope that helps,
rAimund

Question to Transferring Global Settings from Source Systems

1) When we do this steps, we found the following information as follows, so the question is that which fields that we should maintain?
BW User ALE
Debugging User
BEx order number
Releasest. hier
Monitor initial
Last IDoc no.
Last IS-Nr.
XPRA executed
Lock Mangr Logs
MD: Sing. Rec. Inst
RFC BI Accelerator
2) If we maintain some of fields should we do something before, and how? e.g. we know BW user ALE = aleremote, so should we maintain aleremote user using SU01 both in R/3 and BW before we do Transferring Global Settings from Source Systems
Thanks for the answer.

Is anyone know how to setting Transferring Global Settings from Source Systems, your answer will be high appreciate.

Can we do integration from Responsys System with CRM On Demand?

Hello Team,
I have a marketing System (Responsys) and need to do integration with CRMOD. Has anyone done this integration before or is it possible to do integration with CRMOD?
Appreicate your help!!!!
Som

It is possible to create integration from any system via Web Services, theoreticaly. But you should to create it yourself and it takes a lot of time.

IMac running 10.7.5 and have 2 question marks from old PPC apps, which I cannot locate to remove from the system? Any suggestions please?

iMac running 10.7.5 and have 2 question marks from old PPC apps, which I cannot locate any links to remove from the system? Any suggestions please?

Hello, if those Question marks are in the Dock, it means OSX can't find them either.
Right click on the Q mark & choose Remove from Dock, might be Roght click or click, then Options>Remove from dock on later OSX versions.
Sometimes you can just drag it of the Dock, or CMD +drag it off.

I too don't want to send my 1st gen nano in unless I get a 1st gen back (others won't charge from my car integration system). Anyone know how to contact Apple to get this answer??

I too don't want to send my 1st gen nano in unless I get a 1st gen back (others won't charge from my car integration system). Anyone know how to contact Apple to get this answer??

iPod nano (1st generation) Replacement Program

Question about Removing Permissions from the System Folder with chmod

Hi
I have a question about the removal of permissions from the System folder (and sub directories and files).
Background
Since installing a new HD, clean install of 10.6, application of updates and moving over backed up user directories I have had several issues with permissions.
I have read several threads on this and using disk warrior and other tools I have been able to fix most of the issues.
The Problem
The issue that remains is a permissions check using Disk Utility keeps reporting
ACL found but not expected on "System".
followed by an extensive list of sub directories and all.
Attempts to repair take hours and the same errors are reported.
Found Solutions
I have read about changing and/or completely removing the ACL from the permissions from the System using two different commands:
sudo chmod -R -N ./System/* ( to remove all ACLs)
or
sudo chmod -R -E ./System/* ( to replace all ACLs )
My Question is ( to the UNIX gurus):
What is the difference between the usage with -E and -R and which is the best approach for a Systems directory and (subordinates)?
Many thanks!!

OK
So I misread on the your instructions about the PW reset, did it, no harm in that. I did also select the options to reset all the permissions for all the accounts and the ACL issues were not resolved. My bad, I forgot to note that.
You do suggest getting and expert opinion but alas these are rather elusive. In most cases the Apple solutions is to do a complete reinstall... I have found that unless you completely wipe a drive and rebuild everything there are often artifacts left behind. Since I have full and redundant back-ups I would rather explore and hack a little instead of a dull old system reinstall. The irony is the system issue I had was it was the result a reinstall and combo update on a new drive. I recognize the risks of entering the realms of the System folders but I am willing to explore knowing full well that I have a path to recovery.
Thanks again for your insights. I come to the forums looking for insights and ideas but not a lecture...

Integrating commitments from external systems

We are working with Project costing 10.7. We are trying to integrate commitements from other systems. Projects supports this (page 11-420 of the User's guide).
We have changed the pa_commitment_txns_v to include the commitments stored in our custom table that we created. We have also ran the projects process that updates PSI. The problem is that our external commitments DO NOT show up in PSI.
I have checked the PAXURVPS for in PSI that calls the views to display in PSI. From what I can tell is that all relevent views call a table called PA_COMMITMENTS_TXNS. No reference is made to the PA_COMMITMENTS_TXNS_V. Any suggestions?
Thanks,
Robert

I am also facing the same issues.
Please let us know if you find any solution

Uploading data from Legacy system

Hi
i am shorthly going to work on data migration project. I have never worked on a data migration project and want to know the answers for the following questions.
1] which technique i must first consider in data upload ( both master data and transaction data )
2] What steps are involved?
3] I know we can use LSMW, BAPI's , BDC , Direct Input , IDOC etc but want to know which one choose and when?
4] What care must be taken in each data migration
5] is there is std list of programs or a good document on when to choose what?
~SR

Hi,
Data migration can be done by the follwoing methods:
LSMW : for master data migartion or small data migartion
BAPI : its just like a FM , thru which u can create master aswell as Transactional data.
u have to import some paremetre as well as tables if required, and Bapi will RETURN the message saying so and so material/delievry had cretaed.
BDC : in BDC we got 2 methods.
CAll transaction and session.
CAll transacton : using this u can uplaod transcational data as well as master data.
the updation can be synchronus or asynchronus updates.
Session: using this u can uplaod transcational data as well as master data.
The updation in session is synchronus, so its time taking process.
Most of the time we go for Call transcation In real situations.
Dircet input method: its out dated.no longer it is being used.
in all the above cases, data is alraedy existing in flat file and u r going to migrate the data in one shot but IDOC is used where the dynamical data migration is necessary.
suppose say ones the material is craeted in legacy sytem , that particulat matreial shud be migarted to R/3.this can be handled thru IDOC.
Idoc: master data as well as Trnascational data is migarted thru IDOC( matmas, orders).
Idoc uses ALE technology in migartion of idoc.
Revert back if any issues.
Check these links.
SAP Data Migration with LSMW
http://www.sap-img.com/sap-data-migration.htm
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
LSMW
No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
So although it was designed for uploading of legacy data it is not restricted to this use.
We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.
The SAP transaction code is 'LSMW' for SAP version 4.6x.
For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.
You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.
If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw
The LSM Workbench carries out the following tasks:
Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)
Converts the data from the source format into the target format
Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is only possible when you are working onlineUpload Condition Pricing
LSMW STEPS
Data Cleansing
Data cleansing allows you to compare, include and merge redundant business partner master records (potential duplicates) in data cleansing cases. Following the data cleansing process you can remove data records from the system using archiving.
Integration
Before you can carry out data cleansing, you must determine the redundant data in your system and include it in data cleansing cases.
You have the following options for duplicate recognition and creation of data cleansing cases.
The Business Address Services (BAS) provide interfaces for integrating the relevant external software (search machines).
User-defined programs
Services of data providers, who check their data for possible duplicates.
In the options described above, the data cleansing cases are created via the system and put into the data cleansing worklist for further processing.
In individual cases you can find potential business partner duplicates in the hitlist of the business partner search and create a separate data cleansing case.
After connecting the non-SAP software (search engines), the system starts duplicate recognition (Delta Scan) with every change to or new entry of a business partner for this specific individual record. You should do a full scan through the complete dataset at the beginning of the consolidation process using the non-SAP software, this registers all potential duplicates in data cleansing cases and makes them available or further processing.
Within the application basis, the referencing objects, which are taken into account by the data cleansing, are limited to the sub-objects of the business partner. You have the possibility to make modification-free enhancements to the referencing objects.
Prerequisites
You must have determined the redundant data records in your system.
To use the interface of the Business Address Services, make the following Customizing settings: SAP Implementation Guide -> Basis -> Basis Services -> Address Management -> Activate Duplicate Check Index Pool
Make the following system settings in the IMG of the SAP Business Partner: Basic Settings -> Data Cleansing -> Maintain Number Range / Define Priorities / Activate Data Cleansing.
Activities
Register data cleansing cases via BAPIs or create them in the dialog for business partner maintenance from the worklist or the business partner search.
Process the created data cleansing cases in a separate process step afterwards.
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
The first is when application data to be replaced is transferred at once, and only once.
The second situation is to transfer data periodically from external systems to SAP and vice versa.
There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
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
EDIT BATCH INPUT  SERVICES SYSTEM
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
Define jobs Jobs  Administration Tools
Or
System Jobsservices
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.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
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.
Flat file can be created in your hard disk as follows:
1 Vinod Krishna Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = C:FF.TXT
FILE TYPE = ASC
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION BDC_OPEN_GROUP
EXPORTING
CLIENT = SY-MANDT
GROUP = POTHURI
HOLDDATE = DATE1
KEEP = X
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. Populating BDCDATA Table
CALL FUNCTION BDC_INSERT
EXPORTING
TCODE = TFBA
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION BDC_CLOSE_GROUP
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = X.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = SCUSTOM-ID
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = /5.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = X.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-NAME.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-CITY.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = SAVE.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. GENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, Populating BDCDATA Table
Call transaction TFBA using BCDDATA Mode A Update S.
REFRESH BDCTAB
ENDLOOP.
check this link:
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sap-img.com/bdc.htm
www.sappoint.com/abap/bdcconcept.pdf
www.sap-img.com/abap/learning-bdc-programming.htm
www.sap-img.com/abap/question-about-bdc-program.htm
www.sapdevelopment.co.uk/bdc/bdchome.htm
www.planetsap.com/bdc_main_page.htm
Re: bdc mm01
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/fa/097119543b11d1898e0000e8322d00/frameset.htm
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
IDOC
What is IDOC ?
IDoc
Standard SAP format for electronic data interchange between systems (Intermediate Document). Different message types (such as delivery confirmations or purchase orders) normally represent different specific formats, the IDoc types. However, multiple message types with related content can be assigned to one IDoc type: For example, the IDoc type ORDERS01 transfers the logical message types ORDERS (purchase order) and ORDRSP (order confirmation).
Also check these link it will help you.
idoc information
http://help.sap.com/saphelp_nw2004s/helpdata/en/78/21785851ce11d189570000e829fbbd/frameset.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
ALE/ IDOC/ XML
Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm - collecting IDocs without BPM
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
Hope it will be useful to u....plz don't forget to reward points...!!!!
Regards
Vasu

Technical platform for Question and answer system

Hello everone!
We are looking for a technology solutions to realize a question and answer module.
Short discription of the functionality we are looking for:
- member can post a question
- this is forwarded to all members via email
- direct answers via email are returned to asker and to the system (--> automatically generate Q&A list)
- system should import/be integrated with distribution list members
I have heard that some requirements will be met by JIVE forums software which comes with NetWeaver 2004s, but I dont know any details (when? where to test?).
Now I wanted to ask if you know a system like this or have experience with question and answer systems and can give us some hints. Would be very nice to hear from you.
Kind regards
Tilman
Business Consulting Knowledge Management

Here's another variant. You're going to have some answers that are the same for multiple questions. Standard text like 'The SYSTEM tablespace'. Now for some questions that is the correct answer and for others it is the incorrect answer.
So now what we have is:
create table questions (q_id number, q_text varchar2(255), primary key (q_id))
create table answers (a_id number, a_text varchar2(255), primary key (a_id))
create table q_a
(q_id number
 , a_id number
 , a_order char(1)
 , correct_yn char(1)
 , primary key (q_id, a_id)
 , check (a_order in ('A', 'B', 'C', 'D'))
 , check ( correct_yn in ('Y', 'N')))
/Obviously we need foreign keys too. You also need a check for uniqueness of the answers' ordering; a recent entry on the Amis blog could help you here. While your at it you need to check that every question has the correct number of putative answers and at least one correct answer.
Cheers, APC

Save Data from other system

Hi,
We have one dot net system and one java system doing our core business.
I want to save data(which is updated daily) from these systems and save into SAP. Not flat files. I want live data sync.
How is this possible.
Thanks,
Swetha

Hi Swethan,
I don't understand your question. If you want real-time integration then you would more than likely be using webservice communication between these systems.
Do you have something specific that you want to understand?
Regards, Trevor

REG:REGRESSION & SYSTEM INTEGRITY TEST

Hi experts,
i have one question i dont know it may be basic question. i am new to xi/pi can you please tell me
how we test & what the purpose of the REGRESSION TEST,SYSTEM INTEGRITY TEST,PERFORMANCE TEST
what are the differences between these three test in pi
thanks in advance
koti

Hi
From the point of view of PI landscape and testing methodologies :
Performance testing
1.To Test the systems load tolerance .Its purely physical testing and no application logic is tested in this.One case may be to check the system performance like how much time is taken if multiple users assess the system or say create orders using the interface.
2.There may be several ways u can design an interface to make the business logic to work.(say with BPM or without BPM).So in PT you can evaluate system performance and decide on which approach is best suited.
3. It might be useful to fix any hardware sizing issues also.
4.Usually done in pr- prod system say after a system refresh or migration etc.
System Integration Testing--
1. To test end to end business logic and functionality when all the systems in the data flow are connected and individual unit test is already done (say ECC,PI and third party ).
2. helps is checking the connectivity, execution of functionality.Basically it can be a functionality test.
3.Done after Dev and before User acceptance testing.
Regression testing----
1. Its done when there are changes made to functionality/data , before and after test scripts are prepared and executed.
2.its helps in checking if the changes made will effect any exisiting functionality ,basically before and after the change the existing functionality should not effect but the required changes should reflect.
3.Done after a fix in code and before moving it to prod.
You can refer this like alsohttp://wiki.sdn.sap.com/wiki/display/ERPLO/TypesofTestings
Best Regards,
Srinivas

How to delete file from other system(LAN)

Hello folks,
Cud u plz help me out in finding code for deleting a file from other system i.e in LAN,assuming that the connection is already established to that system.

> Cud u plz
sigh
Please make the extra effort to write out words such as "could", "you", and "please". The extra keystrokes won't cost much in the way of time, and the enhanced clarity will be appreciated by those communicating on a forum with international readership. Also, it will give the appearance that you take your question seriously, which will in turn make your question look more interesting to answer.
Thanks!
~

Question from a System Integrator

Similar Messages

Maybe you are looking for