Explain the procedure to create PR or PO by MRP?

Dear sir
please Explain the procedure to create PR or PO by MRP?

Hi,
you can analyze your stock and requirements with MD04 transaction.
PR is generated automaticaly through MRP
you want specifc help, then tell what settings you have made in material master MRP1 view and describe the MRP elements that are listed in MD04.
Compare MD04 and MD05 for the particular material.in MD05 shows the results of the last MRP run and all the PR shown is the MRP
generated.
Now for the same material check in MD04 and in case if there are additional PR after compairing with Md05,you can conclude the
manually generated PR and MRP generated PR.
If you need to check, whether RV is maintained as the document in the configuration of MRP groups, if it is not maintained in any of the MRP groups, then a document with RV can never be created with MRP.
Regards
Raj.

Similar Messages

Can any share me the procedure to create a text box in screen painter?

Hi Friends,
Can anyone share me the procedure to create a text box in screen painter and browser for attaching files ....please its urgent....
Points will be definetly rewarded.
Thanks

Refer to
How to create a text box in ascreen painter?
where another user (venkateshwar reddy) has asked a very similar question... is this an exam question?
Jonathan

What is the procedure to create field catalog in alv

what is the procedure to create field catalog in alv?
with a example please.

Hi,
U can use the function module REUSE_ALV_FIELDCAT_MERGE...If we use a structure that is exactly
identical to the datadictionary other wise u hav to hard code as in the following example.
**ALV EXAMPLE
*& Report ZJE_ALV_EXAMPLE
REPORT zje_alv_example.
TYPE-POOLS: slis.
*type declaration for values from ekko
TYPES: BEGIN OF i_ekko,
 ebeln LIKE ekko-ebeln,
 aedat LIKE ekko-aedat,
 bukrs LIKE ekko-bukrs,
 bsart LIKE ekko-bsart,
 lifnr LIKE ekko-lifnr,
 END OF i_ekko.
*type declaration for values from ekpo
TYPES: BEGIN OF i_ekpo,
 ebeln LIKE ekpo-ebeln,
 ebelp LIKE ekpo-ebelp,
 matnr LIKE ekpo-matnr,
 menge LIKE ekpo-menge,
 meins LIKE ekpo-meins,
 netpr LIKE ekpo-netpr,
 END OF i_ekpo.
DATA: it_ekko TYPE STANDARD TABLE OF i_ekko INITIAL SIZE 0,
 wa_ekko TYPE i_ekko.
DATA: it_ekpo TYPE STANDARD TABLE OF i_ekpo INITIAL SIZE 0,
 wa_ekpo TYPE i_ekpo .
*variable for Report ID
DATA: v_repid LIKE sy-repid .
*declaration for fieldcatalog
DATA: i_fieldcat TYPE slis_t_fieldcat_alv,
 wa_fieldcat TYPE slis_fieldcat_alv.
DATA: it_listheader TYPE slis_t_listheader.
declaration for events table where user comand or set PF status will
be defined
DATA: v_events TYPE slis_t_event,
 wa_event TYPE slis_alv_event.
declartion for layout
DATA: alv_layout TYPE slis_layout_alv.
declaration for variant(type of display we want)
DATA: i_variant TYPE disvariant,
 i_variant1 TYPE disvariant,
 i_save(1) TYPE c.
*PARAMETERS : p_var TYPE disvariant-variant.
*Title displayed when the alv list is displayed
DATA: i_title_ekko TYPE lvc_title VALUE 'FIRST LIST DISPLAYED'.
DATA: i_title_ekpo TYPE lvc_title VALUE 'SECONDRY LIST DISPLAYED'.
INITIALIZATION.
v_repid = sy-repid.
PERFORM build_fieldcatlog.
PERFORM event_call.
PERFORM populate_event.
START-OF-SELECTION.
PERFORM data_retrieval.
PERFORM build_listheader USING it_listheader.
PERFORM display_alv_report.
*& Form BUILD_FIELDCATLOG
Fieldcatalog has all the field details from ekko
FORM build_fieldcatlog.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'EBELN'.
wa_fieldcat-seltext_m = 'PO NO.'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'AEDAT'.
wa_fieldcat-seltext_m = 'DATE.'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'BUKRS'.
wa_fieldcat-seltext_m = 'COMPANY CODE'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'BUKRS'.
wa_fieldcat-seltext_m = 'DOCMENT TYPE'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'LIFNR'.
wa_fieldcat-no_out = 'X'.
wa_fieldcat-seltext_m = 'VENDOR CODE'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
ENDFORM. "BUILD_FIELDCATLOG
*& Form EVENT_CALL
we get all events - TOP OF PAGE or USER COMMAND in table v_events
FORM event_call.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
i_list_type = 0
IMPORTING
et_events = v_events
EXCEPTIONS
LIST_TYPE_WRONG = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. "EVENT_CALL
*& Form POPULATE_EVENT
Events populated for TOP OF PAGE & USER COMAND
FORM populate_event.
READ TABLE v_events INTO wa_event WITH KEY name = 'TOP_OF_PAGE'.
IF sy-subrc EQ 0.
 wa_event-form = 'TOP_OF_PAGE'.
 MODIFY v_events FROM wa_event TRANSPORTING form WHERE name =
 wa_event-form.
ENDIF.
READ TABLE v_events INTO wa_event WITH KEY name = 'USER_COMMAND'.
IF sy-subrc EQ 0.
 wa_event-form = 'USER_COMMAND'.
 MODIFY v_events FROM wa_event TRANSPORTING form WHERE name =
 wa_event-name.
ENDIF.
ENDFORM. "POPULATE_EVENT
*& Form data_retrieval
retreiving values from the database table ekko
FORM data_retrieval.
SELECT ebeln aedat bukrs bsart lifnr
 FROM ekko
 INTO TABLE it_ekko.
ENDFORM. "data_retrieval
*& Form bUild_listheader
text
-->I_LISTHEADEtext
FORM build_listheader USING i_listheader TYPE slis_t_listheader.
DATA hline TYPE slis_listheader.
hline-info = 'this is my first alv pgm'.
hline-typ = 'H'.
ENDFORM. "build_listheader
*& Form display_alv_report
text
FORM display_alv_report.
v_repid = sy-repid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = v_repid
I_CALLBACK_PF_STATUS_SET = ' '
i_callback_user_command = 'USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
i_grid_title = i_title_ekko
I_GRID_SETTINGS =
IS_LAYOUT = ALV_LAYOUT
it_fieldcat = i_fieldcat[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
i_default = 'ZLAY1'
i_save = 'A'
is_variant = i_variant
it_events = v_events
TABLES
t_outtab = it_ekko
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. "display_alv_report
*& Form TOP_OF_PAGE
text
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = it_listheader
i_logo =
I_END_OF_LIST_GRID =
ENDFORM. "TOP_OF_PAGE
*& Form USER_COMMAND
text
-->R_UCOMM text
-->, text
-->RS_SLEFIELDtext
FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.
CASE r_ucomm.
 WHEN '&IC1'.
 READ TABLE it_ekko INTO wa_ekko INDEX rs_selfield-tabindex.
 PERFORM build_fieldcatlog_ekpo.
 PERFORM event_call_ekpo.
 PERFORM populate_event_ekpo.
 PERFORM data_retrieval_ekpo.
 PERFORM build_listheader_ekpo USING it_listheader.
 PERFORM display_alv_ekpo.
ENDCASE.
ENDFORM. "user_command
*& Form BUILD_FIELDCATLOG_EKPO
text
FORM build_fieldcatlog_ekpo.
wa_fieldcat-tabname = 'IT_EKPO'.
wa_fieldcat-fieldname = 'EBELN'.
wa_fieldcat-seltext_m = 'PO NO.'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKPO'.
wa_fieldcat-fieldname = 'EBELP'.
wa_fieldcat-seltext_m = 'LINE NO'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'I_EKPO'.
wa_fieldcat-fieldname = 'MATNR'.
wa_fieldcat-seltext_m = 'MATERIAL NO.'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'I_EKPO'.
wa_fieldcat-fieldname = 'MENGE'.
wa_fieldcat-seltext_m = 'QUANTITY'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'I_EKPO'.
wa_fieldcat-fieldname = 'MEINS'.
wa_fieldcat-seltext_m = 'UOM'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'I_EKPO'.
wa_fieldcat-fieldname = 'NETPR'.
wa_fieldcat-seltext_m = 'PRICE'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
ENDFORM. "BUILD_FIELDCATLOG_EKPO
*& Form event_call_ekpo
we get all events - TOP OF PAGE or USER COMMAND in table v_events
FORM event_call_ekpo.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
i_list_type = 0
IMPORTING
et_events = v_events
EXCEPTIONS
LIST_TYPE_WRONG = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. "event_call_ekpo
*& Form POPULATE_EVENT
Events populated for TOP OF PAGE & USER COMAND
FORM populate_event_ekpo.
READ TABLE v_events INTO wa_event WITH KEY name = 'TOP_OF_PAGE'.
IF sy-subrc EQ 0.
 wa_event-form = 'TOP_OF_PAGE'.
 MODIFY v_events FROM wa_event TRANSPORTING form WHERE name =
 wa_event-form.
ENDIF.
ENDFORM. "POPULATE_EVENT
*& Form TOP_OF_PAGE
text
FORM f_top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = it_listheader
i_logo =
I_END_OF_LIST_GRID =
ENDFORM. "TOP_OF_PAGE
*& Form USER_COMMAND
text
-->R_UCOMM text
-->, text
-->RS_SLEFIELDtext
*retreiving values from the database table ekko
FORM data_retrieval_ekpo.
SELECT ebeln ebelp matnr menge meins netpr
 FROM ekpo
 INTO TABLE it_ekpo.
ENDFORM. "DATA_RETRIEVAL_EKPO
*& Form BUILD_LISTHEADER_EKPO
 text
 -->I_LISTHEADER text
FORM build_listheader_ekpo USING i_listheader TYPE slis_t_listheader.
DATA: hline1 TYPE slis_listheader.
hline1-typ = 'H'.
hline1-info = 'CHECKING PGM'.
ENDFORM. "BUILD_LISTHEADER_EKPO
*& Form DISPLAY_ALV_EKPO
 text
FORM display_alv_ekpo.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER = ' '
I_BUFFER_ACTIVE = ' '
i_callback_program = v_repid
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = 'F_USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
I_CALLBACK_HTML_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_END_OF_LIST = ' '
I_STRUCTURE_NAME =
I_BACKGROUND_ID = ' '
i_grid_title = i_title_ekpo
I_GRID_SETTINGS =
IS_LAYOUT =
it_fieldcat = i_fieldcat[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT =
i_save = 'A'
IS_VARIANT =
it_events = v_events
TABLES
t_outtab = it_ekpo
EXCEPTIONS
program_error = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. "DISPLAY_ALV_EKPO
Reward if Helpful

What is the Procedure for Creating BC sets In PI

hi
what is the Procedure for Creating BC sets In PI
Thanks

Hi Venkata,
Read this SAP official document on creating BC Sets:
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/6f/3c3f91fbef11d2958c00a0c930dcc1/frameset.htm">http://help.sap.com/saphelp_nw04s/helpdata/en/6f/3c3f91fbef11d2958c00a0c930dcc1/frameset.htm</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/6f/3c3f88fbef11d2958c00a0c930dcc1/frameset.htm">Create Business Configuration Sets</a>
Regards,
Subhasha Ranjan

Hi friends can i know the procedure to create a web browser?

HI friends, i am ABAPer and i want to know how to create attachment BROWSER like what we attach for any documents over mail.
Example when we click on browser the path of the computer has to be opened and by giving the document name attach and the document will be attached. Please tell me the procedure....
or let me know to which form i have to post my query..

Hi,
If you want any useful answer you may need to rewrite your question.
I did not understand anything about your question and I guess that I may not be the only one !
Regards,
Olivier

What is the Procedure to Create "Condition Value" Routine Using VOFM

Dear Guru,
I want to know Step-By-Step Procedure to Create "Condition Value" Routine Using VOFM.
Give me guideline how it will link to program RV64ANNN.
and if it doesnot link to RV64ANNN
what might be the possible reason and how to make it link with RV64ANNN.

Dear Guru.
I have encountered a technical issue related to Creation of User Routine for pricing procedure
(Routine :: RV64A978).
Before coming to issue I want to give you slight glance on my requirement.
I have got two requirements to write two routines for a new condition type -->> packing type .
>>Routine Number One First I Have wrote Requirement Routine         RV61A943
Routine Number two  Other I Have wrote calculate condition value  RV64A978
So as usual normal procedure of writing a routine I followed VOFM for writing routine for pricing procedure and routine for calculation (condition value).
I performed above respective process for both routines in VOFM.
And I have activated both routine from going VOFMMenu bar edit  Activate.
After activation automatic include is generated in both case .
INCLUDE RV61A943 . "FAMD PAckage Wt
Is generated in RV61ANNN
INCLUDE RV64A978 . "FAMD Package-Rate
Is generated in RV64ANNN
In case of Routine  RV61A943
I can able to find the main include routine RV61ANNN from where used function in SE38 and able to trace it.
And I am able to find it in the lists of Includes of RV61ANNN.
But In case of Routine  RV64A978
I can not able to find the main include routine RV64ANNN from where used function and able to trace it. Pls refer below picture.
But in RV64ANNN it is showing that routine RV64A978 is there 
So Guru I want to know following things >
1.     What might be the main reason in case of RV64A978 ??
2.     How I should approach to solve this issue??
Because what I understood unless routine RV64A978 is traceable from u201Cwhere usedu201D to find out its main routine RV64ANNN , the routine RV64A978 wont work in pricing procedure (I believe).

What is the procedure to create entry in NAST table for particualr document

Hello ABAP GURUS,
I need to know how to create objectkeys in NAST table for particualar document number.
My requirement is i need to check my smartform output for Goods Receipt.IN nast table,i dont have any entries for Goods Receipt.So i need to create entries in NAST table.Please help me to solve this problem.
waiting for your replies
Regards
Maruthi

Hi!
Ususally it is not neccessary to create manual entries in NAST.
You have to print the document from its transaction. Naturally there may be some other settings which are required after setting transaction NACE.
If you understand the Letter of delivery on the Goods Receipt, which can be printed from VL02N, then you have to set some automation to your printing using transaction VV22.
Regards
Tamá

Can any body tell the procedure to create CHARTS in SAP eSourcing!! Thanks.

Hi ,
I am new to eSourcing.
I have a requirement of creating CHARTS like BAR or PIE charts.
Please help me out
Thanks in advance !!!
Edited by: Vijay Durgam on Sep 24, 2009 2:51 PM

Hi ,
I am new to eSourcing.
I have a requirement of creating CHARTS like BAR or PIE charts.
Please help me out
Thanks in advance !!!
Edited by: Vijay Durgam on Sep 24, 2009 2:51 PM

Procedure for creating credit memo for sales return

Dear Gurus,
Please let me know the procedure creating a credit memo for sales returns.
I am able to cancel the invoice using vf11. create a return sales order using vao1. create a retrun delivery using vl01n, transfer the stock from returns to blocked to unrestricted use using mb1b and movement types 459 and 343.
Pls let me know the procedure for creating the credit memo for the goods receipt of sales return.

Dear,
         I am not geeting your question but well i explain in my company scenarion,
    1)    We create the Sales Order : VA01 ( Order type : ZREW : Return without invoice, ZRES : Return with Invoice)
            Here, ZREW is our own created order type and it is maintain in config.
                     ZRES is use for Return with invoice. In that we enter the bill number in return sales order which sales.
    2)    In Delivery : VL01N : That is base on Return Sales order.
    3)    In Billing   : VF01 : Create credit memo with resp. to delivery number.
                  Credit memo type : Same as sales order,
                                                ZREW : Crd Return (W/O Inv)
                                                ZRES : Credit For Returns.
Hope it will help you.
Regards,
Sandip

What is the procedure for scheduling agreements, for manual entry

dear sirs,
pls explain the procedure for scheduling agreements(manual) creating and invoicing.

From the Purchasing menu, choose Outline agreement ® Scheduling agreement ® Create.
The initial screen appears.
Enter the necessary data. Any data you enter under Default Data: Item will appear as default data in each item.
In the Agreement type field you specify whether you are creating a scheduling agreement with or without release documentation, for example. The agreement types LPA (with release documentation) and LP (without release documentation) are defined in the standard system.
Press ENTER.
The header data screen appears.
Enter the duration of the scheduling agreement. Check the other fields on this screen. Make any necessary changes (e.g. the terms of payment) and define the header conditions (see Maintaining Conditions).
Press ENTER.
The item overview screen appears.
Enter the necessary data for each item (material number, target quantity, price, receiving plant, account assignment etc.).
Material without material master record: leave the field for the material number empty and enter the following:
A short description of the relevant material or service in the Short text field
The material group to which the material belongs
The account assignment category (column A)
The target quantity and the order unit
If you specify an account assignment category, you must enter the relevant account assignment data for each item of the scheduling agreement. To do so, choose Item ® Account assignments.
(See also Account Assignment.)
If necessary, review the details for each item. Select the item(s) to review. Then choose Item ® Details to call up the item detail screen.
Enter the desired conditions for the item (discounts, surcharges etc.). To do so, select the item and choose Item ® Conditions.
Enter further text for the item if any additional instructions to the vendor or to Goods Receiving are necessary. Choose Item ® Texts ® Text overview.
Save the scheduling agreement.
Fi you want to use firm zone then
On the scheduling agreement item overview screen, select the item for which you wish to define delivery schedule time zones.
Choose Item ® More functions ® Additional data.
In the Firm zone field, enter a number of days (calculated from the current date) defining the period after whose expiration the firm zone ends and the trade-off zone begins.
In the Trade-off zone field, enter the number of days (calculated from the current date) defining the period after whose expiration the trade-off zone ends and the planning zone begins.
If the firm zone is to cover one month, enter the value 30 (days) in the Firm zone field. If the trade-off zone ends one month after the firm zone, enter the value 60 in the Trade-off zone field.
In the Binding for Materials Planning field, specify whether Materials Planning may change schedule lines that fall within the firm or trade-off zones.
Save your data.
Delivery schadule
Choose Outline agreement ® Scheduling agreement ® Delivery schedule ® Maintain.
The initial screen for the creation of delivery schedules under scheduling agreements appears.
Enter the document number of the scheduling agreement and press ENTER.
The item overview screen for the scheduling agreement appears.
Select the item you wish to schedule. Then choose Item ® Delivery schedule.
Enter the following for each schedule line:
- Date category (Month, Week, or Day) and the corresponding date
- Delivery time-spot (if applicable)
- Quantity to be delivered (the unit of measure is the same as in the scheduling agreement)
Referencing a purchase requisition: Choose Sch. agmt. schedule ® Create w. reference ® To purchase req. to adopt the delivery data from an existing requisition.
Save the delivery schedule.
Invoice is same like PO

Procedure for creating transparent table, data element and domain

Hi,
Can anybody let me know the procedure for creating transparent table, data element and domain.
Thanks,
Mahathi

Hi
Database table and its components
A database table is the central data structure of the ABAP/4 data dictionary.
The structure of the objects of application development are mapped in tables on the underlying relational database.
The attributes of these objects correspond to fields of the table.
A table consists of columns (fields) and rows (entries). It has a name and different attributes, such as delivery class and maintenance authorization.
A field has a unique name and attributes; for example it can be a key field.
A table has one or more key fields, called the primary key.
The values of these key fields uniquely identify a table entry.
You must specify a reference table for fields containing a currency (data type CURR) or quantity (data type QUAN). It must contain a field (reference field) with the format for currency keys (data type CUKY) or the format for units (data type UNIT). The field is only assigned to the reference field at program runtime.
The basic objects for defining data in the ABAP Dictionary are tables, data elements and domains. The domain is used for the technical definition of a table field (for example field type and length) and the data element is used for the semantic definition (for example short description).
A domain describes the value range of a field. It is defined by its data type and length. The value range can be limited by specifying fixed values.
A data element describes the meaning of a domain in a certain business context. It contains primarily the field help (F1 documentation) and the field labels in the screen.
A field is not an independent object. It is table-dependent and can only be maintained within a table.
You can enter the data type and number of places directly for a field. No data element is required in this case. Instead the data type and number of places is defined by specifying a direct type.
The data type attributes of a data element can also be defined by specifying a built-in type, where the data type and number of places is entered directly.
Two Level Domain Example
A domain defines a field technically and therefore it may
be used at different business levels.
A data element describes the meaning of a domain in a certain business context.
A domain, however, is used for the technical definition of a table field (for example field type and length).
Therefore, although a take-off airport (data element S_FROMAIRP) would have a different business meaning from an airport where a plane lands (data element S_TOAIRP), they could still have the same domain(here S_AIRPID) because technically we could assign the same number of characters whether the airport is a take-off or a landing airport.
Definitions of Table in Database
In SAP R/3 tables are defined as
A) Transparent tables: All of the fields of a dictionary table correspond to a field in the real database table.
B) Pooled tables: Different tables which are not linked to each other with a common key are combined into a TABLE POOL. Several logical tables thus exist as a single real database table.
C) Cluster tables: Several tables linked by a common key may sometimes be combined by the data dictionary and made to exist on the database schema as a single table.
SAP is evolving R/3 tables in transparent tables.
Elaboration on each of the definitions
A transparent table is automatically created on the database when it is activated in the ABAP Dictionary. At this time the database-independent description of the table in the ABAP Dictionary is translated into the language of the database system used.
The database table has the same name as the table in the ABAP Dictionary. The fields also have the same name in both the database and the ABAP Dictionary. The data types in the ABAP Dictionary are converted to the corresponding data types of the database system.
The order of the fields in the ABAP Dictionary can differ from the order of the fields on the database. This permits you to insert new fields without having to convert the table. When a new field is added, the adjustment is made by changing the database catalog (ALTER TABLE). The new field is added to the database table, whatever the position of the new field in the ABAP Dictionary.
Tables can also reside on the database as Pooled tables or cluster tables
Pooled Tables: Different tables which are not linked to each other with a common key can be combined into a Table Pool. The tables contained within this pool are called Pooled Tables. A table pool is stored in the database a simple table. The table's data sets contain, in separate fields, the actual key for the data set to be stored, the name of the pooled table and the contents of the data set to be stored.
Using this schema, several logical tables are combined into a single real database table. Although the data structure of each set is lost during the write to the table pool, it is restored during the read by the ABAP/4 Data Dictionary. The ABAP/4 Data Dictionary utilizes its meta-data to accomplish this.
Since information must be prepared (defined) within the ABAP/4 Data Dictionary when it is read or written to (or accessed), this process itself defines these as not transparent tables
Cluster Tables: Occasionally, several tables may be linked by a common key. The ABAP/4 Data Dictionary can also combine these tables into a single table. Each data set of the real table within the database contains a key and in a single data field, several data sets of the subsequent table for this key.
As mentioned above, these table types require special data handling, therefore they are not transparent tables.
Technical Settings in Dictionary
The data class logically defines the physical area of the database (for ORACLE the table space) in which your table should be created. If you choose the data class correctly, the table will automatically be created in the appropriate area on the database when it is activated in the ABAP Dictionary.
The most important data classes are master data, transaction data, organizational data and system data.
Master data is data that is rarely modified. An example of master data is the data of an address file, for example the name, address and telephone number.
Transaction data is data that is frequently modified. An example is the material stock of a warehouse, which can change after each purchase order.
Organizational data is data that is defined during customizing when the system is installed and that is rarely modified thereafter. The country keys are an example.
System data is data that the R/3 System itself needs. The program sources are an example.
Further data classes, called customer data classes (USER, USER1), are provided for customers. These should be used for customer developments. Special storage areas must be allocated in the database.
The size category describes the expected storage requirements for the table on the database.
An initial extent is reserved when a table is created on the database. The size of the initial extent is identical for all size categories. If the table needs more space for data at a later time, extents are added. These additional extents have a fixed size that is determined by the size category specified in the ABAP Dictionary.
You can choose a size category from 0 to 4. A fixed extent size, which depends on the database system used, is assigned to each category.
Correctly assigning a size category therefore ensures that you do not create a large number of small extents. It also prevents storage space from being wasted when creating extents that are too large.
Modifications to the entries of a table can be recorded and stored using logging.
To activate logging, the corresponding field must be selected in the technical settings. Logging, however, only will take place if the R/3 System was started with a profile containing parameter 'rec/client'. Only selecting the flag in the ABAP Dictionary is not sufficient to trigger logging.
Parameter 'rec/client' can have the following settings:
rec/client = ALL All clients should be logged.
rec/client = 000[...] Only the specified clients should be logged.
rec/client = OFF Logging is not enabled on this system.
The data modifications are logged independently of the update. The logs can be displayed with the Transaction Table History (SCU3).
Logging creates a 'bottleneck' in the system:
Additional write access for each modification to tables being logged.
This can result in lock situations although the users are accessing different application tables!
Create transparent table
Go to transaction SE11. Enter name of table you want to create (beginning with Y or Z) and click on create pushbutton
Enter the delivery class and the table maintenance criteria
The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems .
The display/maintenance indicator specifies whether it is possible to display/maintain a table/view using the maintenance tools Data Browser (transaction SE16) and table view maintenance (transactions SM30 and SM31).
Enter the name of the table field and the data element. The
System automatically populates the technical details for
existing data elements.
So far as possible it is advisable to use existing data elements which befit the business requirements.
However, we may create data elements if need be. The same is shown in the next slide.
To create a data element simply double click on it.
Alternately create a data element by simply choosing the
data type radio button on SE11 initial screen.
Create data element
The system prompts you to create a new data element.
Choose the Yes pushbutton.
Under the data type tab enter the domain name which
determines the technical characteristics of the field.
Further characteristics tab: Allows you to specify a search help assigned to the data element.
It also allows you to specify a parameter id which helps you populate a field from SAP memory.
Field label: Can be assigned as prefixed text to a screen field referring to the ABAP Dictionary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
Create domain
If the domain does not exist in the data dictionary the
system prompts you to create one.
Give the technical characteristics under the definition
tab. Value range allows you value restriction at domain
level.
Value range tab:
As explained in the section Consistency through input checks one can restrict the possible values for a field at domain level itself by either entering fixed values or by specifying a value table under the tab Value range.
Currency/Quantity fields in a table
A currency or a quantity field must be assigned a reference field from a reference table containing applicable qty unit or currency unit.
Field of the reference table, containing the applicable quantity unit or currency
A field containing currency amounts (data type CURR) must be assigned a reference field including the currency key (data type CUKY).
A field containing quantity specifications (data type QUAN) must be assigned a reference field including the associated quantity unit (data type UNIT).
Create transparent table continue
Maintain the technical settings of the table by clicking on the tab

Procedure for creating Inbox views

HI All,
Could you please let us know the procedure for creating new Inbox view in BPM 11g.
We have an option to create my Views / Sharing Views in 11g but how we can put that under Inbox views.
Thanks,
Aravind.

Hi Antonis,
We need view under Inbox. PFA. the attached screenshot.
Thanks,
Aravind.

Procedure to create Individual Objects in SAP CRM

Hi Experts,
Can some one please let me know the procedure to create Individual Objects in SAP CRM.
My requirement is like this: I want to create an Individual Object first and then create an Installed base and assign the Individual Object to Installed base.
Regards
Narendra

Hi Narendra,
You might not be able to create an Individual object directly in CRM using the SAP GUI, but the way I know of is to use the PC-UI application CRMM_PRD_IOBJECT. So the URL would be something like:
http://<FQDN>:<port>/sap/bc/bsp/sap/crm_bsp_frame/entrypoint.do?appl=CRMM_PRD_IOBJECT
once you have created your Iobject here you can try to utilize the same in your installed base.
Hope this helps!!
Regards
Piyush
PS:Award Points if useful!!

Not able to execute the procedure

Hi everybody,
I am trying to execute a procedure as below,
CREATE OR REPLACE procedure test1(n1 IN number, n2 IN number, tot OUT number)
is
i number := null;
begin
loop
if n2>n1 then
i:=i+1;
tot:=n1+i;
dbms_output.put_line(tot);
elsif n2<n1 then
dbms_output.put_line('Enter a higher value for n2');
end if;
end loop;
end;
All im trying to do is to print the numbers according to the values we give during the runtime, but doesn't seem to work for me.
ie.,
n1=1;
n2=5;
tot = 1,2,3,4,5;
I am sorry if there are some error's in the procedure and would really appreciate if you can help me with this. Thanks in advance for your help.
Edited by: Pravin on 31 Aug, 2010 2:25 PM

When i run the procedure now,
CREATE OR REPLACE procedure test1(n1 IN number, n2 IN number, tot OUT number)
is
i number := null;
begin
loop
if n2>n1 then
i:=i+1;
tot:=n1+i;
dbms_output.put_line(tot);
elsif n2<n1 then
dbms_output.put_line('Enter a higher value for n1');
end if;
exit;
end loop;
end;
set serveroutput on;
variable tot number;
execute test1(1,4,:tot);
print tot;
Im getting output as,
PL/SQL procedure successfully completed.
tot
Nothing is getting printed now. Any reasons for it. I would like to appreciate everybody's help, by the way. Hope we will find a solution.
Edited by: Pravin on 31 Aug, 2010 2:40 PM

Procedure to create multiple tasks

hi gurus,
             What is the procedure to create the multiple steps taks in workflow and tcode for that.

no i mean in workflow we have 2 types of tasks
1- single step tasks.
2-multiple step tasks.
single step tasks which we create normally.so i want to know how to create the multiple step tasks.i heard that we need to start with-
1.      In the UWL view, choose New Task.
2.      Select Multiple Steps from the Task Type dropdown list.
3.      Under Subject, enter a title for the task.
4.      Choose Add Step.
                                      Here iam unable to get the step 1.please could you tell me the exact procedure.

Explain the procedure to create PR or PO by MRP?

Similar Messages

Maybe you are looking for