-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- SAP Business Suite
- Artificial Intelligence
- Business applications
- Data and analytics
- Technology Platform
- Financial Management
- Spend Management
- Supply Chain Management
- Human Capital Management
- Customer Experience
- SAP Business Network
- View products A-Z
- View industries
- Try SAP
- Partners
- Services
- Learning and Support
- About
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
BDC Session
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2007 Jan 25 6:08 AM
- SAP Managed Tags
- ABAP Development
Hi Friends,
In BDC session is used to perform huge database updations using more than one transaction and which will last for a long time.Can you please expalin me how is this possible in Session method.
Reagrdsm
Dinesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2007 Jan 25 6:34 AM
- SAP Managed Tags
- ABAP Development
Hi,
In session method basically what you will do is, you populate the fields (data) of the screens and submit the job to run in back ground, then it will update them one by one.
Ex: see in MM01 you can straight away create one material at one time, but screens and fields involved are more and it is bit complex.
So when you want to create materials in mass (could be existing in legasy system) you will simulate screen movements and mandatory fields either by recording (SHDB) or manually walking over all the screens required and mandatory fields. This is equivalent crerating a session. Once data is added from file then there would be multiple sessions and if more than one transaction is used you have to code them in the order of dependencies.
Finally all will be processed ususally in BG mode as it is a huge process of time consuming.
Please feel free to revert in case more elaboration is needed.
-B S B
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2007 Jan 25 6:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2007 Jan 25 6:21 AM
- SAP Managed Tags
- ABAP Development
hi,
check this link
http://help.sap.com/saphelp_47x200/helpdata/en/69/c2508f4ba111d189750000e8322d00/frameset.htm
pLZ reward ih helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2007 Jan 25 6:34 AM
- SAP Managed Tags
- ABAP Development
Hi,
In session method basically what you will do is, you populate the fields (data) of the screens and submit the job to run in back ground, then it will update them one by one.
Ex: see in MM01 you can straight away create one material at one time, but screens and fields involved are more and it is bit complex.
So when you want to create materials in mass (could be existing in legasy system) you will simulate screen movements and mandatory fields either by recording (SHDB) or manually walking over all the screens required and mandatory fields. This is equivalent crerating a session. Once data is added from file then there would be multiple sessions and if more than one transaction is used you have to code them in the order of dependencies.
Finally all will be processed ususally in BG mode as it is a huge process of time consuming.
Please feel free to revert in case more elaboration is needed.
-B S B
Bluesky