OPEN DATA SET

[Former Member]

Hi ALL,

I want know this questions plz give me answer ?.

1.What is open data set. what perpose we use this one.

2.What is d/w SE09 and SE10.

3.What is ment by FOR ALL ENTRIES.

4.How handle error's in BDC call transaction method.

5.What ment by FILTERTYPE BADI.

6.What is d/w user-exit and customer-exit.

7.Explian the SD flow and MM flow.

Thanks & Regrads,

srinivas

[Former Member · Accepted solution]

Hi Srinu,

1. About Open dataset

- Datasets are the files stored in Application server

For ex, if u want to store data from presentation server to internal table, we use 'GUI_UPLOAD' function module

but to store at Application server, we have to use abap statement 'OPEN DATASET'

if u want in detail, how to store data to appl.server, i can provide you abap program for that.........

2. Functionalities of SE09/10 are the same i.e. to transport requests from development client to testing client

3. FOR ALL ENTRIES - It provides you set of selection statements which matches for the given condition against entries in the check table.

4. Error handling in BDC call transaction - use the structure BDCMSGCOLL

7. SD flow

1. Enquiry creation - TCode VA11

2. Quotation creation - VA21

3. Sales Order creation - VA01

4. Delivery Form - VL01N

5. Post Goods Issue - VL09

6. Shipping - VT01

7. Billing / Invoice - VF01

MM flow

1. Purchase requisition - ME51N

2. Request for Quotation - ME41N

3. Quotation creation - ME47

4. Quotation comparison - ME49

5. Purchase Info Record creation - ME11

6. Purchase Order creation - ME21N

7. Goods Receipt - MIGO

8. Invoice verification - MIRO

9. Vendor payments - F-44

Reward me points if it helpful to you

Thanks

Suren

[Former Member]

Hai,

Open dataset is used to open an application server file.

SE09 and SE10 are used to transport the modified objects(requests)

from development server to testing server or production server.

For all entries is used to fetch common data. For all entries in table1 where table1-field1 = table2-field1. But the first table table has data in it. and also common matching data field1 in both the tables.

We can handle errors in call transaction explicitly.

data: it_errors like bdcmsgcoll occurs 0 with headerline.

call transaction <tcode> using itab messages into it_errors.

User exits are userforms in which system provided include we have to write the code. Customer exits are the exits for which we have to create a project. they are like hooks.

MMflow:

1. purchase requisition

2. Request for quotation

3. Quotation

4. Purchase order

5. Goods receipt

6. Invoice verification

7. Payment

SD flow:

1. Inquiry

2. Quotation

3. Sales order

4. Delivery

5. Goods issue

6. Invoicing

Regards,

Kamala.