SAP Desk Creation, Upkeep, and Authorization – Insta News Hub

Creating Personalized Tables for Desk Upkeep

Go to SE11 and provides the desk identify that you simply need to create.

Give the Description of the desk and enter the next particulars.

1. Supply Class

Supply Class Used For

• A – Software desk (grasp and transaction knowledge).
• C -Buyer desk: knowledge is maintained by the client solely
• L  – Desk for storing short-term knowledge
• G  – Buyer desk, SAP might insert new knowledge information, however might not overwrite or delete present knowledge information. The shopper namespace have to be outlined in desk TRESC. (Use Report RDDKOR54 right here).
• E – System desk with its personal namespaces for buyer entries. The shopper namespace have to be outlined in desk TRESC. (Use Report RDDKOR54 right here.)
• S – System desk, knowledge adjustments have the identical standing as program adjustments.
• W – System desk (e.g. desk of the event surroundings) whose knowledge is transported with its personal transport objects (e.g. R3TR PROG, R3TR TABL, and many others.).

2. Information Browser/Desk View Maint.

Choices Obtainable

1. Show/upkeep not allowed: The utilization of ordinary desk upkeep instruments isn’t allowed.
   • Upkeep and show of this Dictionary object isn’t attainable in transaction SE16.
   • Transaction SE54 doesn’t enable the era of a upkeep dialog, which implies routinely calling transactions SM30/SM34 for this Dictionary object is not attainable.
2. Show/upkeep allowed to restricted extent: Utilization of ordinary desk upkeep instruments is allowed to a restricted extent.
   •  Transaction SE16 permits the show perform for this Dictionary object, however no upkeep.
   • Era of a upkeep dialog for this Dictionary object is feasible utilizing transaction SE54.
   • Transaction SM30 doesn’t enable upkeep and show features for this Dictionary object
3. Show/upkeep allowed: The utilization of ordinary desk upkeep instruments is allowed:
   • Transaction SE16 permits the upkeep and show features for this Dictionary object. Notice: If an SM30 upkeep dialog exists for this Dictionary object, it’s referred to as.
   • Transaction SE54 permits the era of a upkeep dialog for this Dictionary object.
   • Transaction SM30 permits the show and upkeep features for this Dictionary object.

Enter the Fields of the desk.

Significance of the Above fields:

• LASTCHANGED: Username of the one that created or modified the information.
• CHANGEDATE: The date on which the information was created or modified.
• CHANGE_TIME: The time on which the information was created or modified.
• COMMENTS: The rationale for the adjustments made to be specified by the person.

As soon as all of the fields have been entered then, click on on Technical Settings and enter the next particulars on the following display:

Information Class

The information class defines the bodily space of the database (for ORACLE, the TABLESPACE) by which your desk is logically saved. When you select a knowledge class accurately, your desk will routinely be assigned to the right space when it’s created on the database.

An important knowledge lessons are (aside from the system knowledge):

• APPL0: Grasp knowledge
• APPL1: Transaction knowledge
• APPL2: Organizational and customizing knowledge

Grasp knowledge is knowledge that’s regularly learn however not often up to date. Transaction knowledge is knowledge that’s regularly up to date. Organizational and customizing knowledge is knowledge that’s outlined when the system is initialized after which not often modified.

Two extra knowledge lessons can be found, USR and USR1. These are reserved for person developments, and the tables assigned to those knowledge lessons are saved in a desk house for person developments.

Notice: The information class solely has an impact on desk storage for the database techniques ORACLE and INFORMIX.

Dimension Class

The dimensions class determines the possible house requirement for a desk within the database.

You may choose classes 0 to 4 in your desk. Every class is assigned a particular fastened storage space worth within the database. While you create a desk, preliminary house is saved for it within the database. If extra space is required later resulting from knowledge that has been entered, the space for storing is elevated in accordance with the class chosen.

Press F4 on the sphere measurement class to see the variety of knowledge information that may be maintained for the person classes of your desk with out problems ensuing. These problems could possibly be for instance a reorganization changing into mandatory as a result of the utmost house to be reserved for the desk was exceeded as a result of maintained measurement class.

Buffering Standing

The buffering standing specifies whether or not or not a desk could also be buffered.

This is dependent upon how the desk is used, for instance, on the anticipated quantity of information within the desk or on the kind of entry to a desk (primarily learn or primarily write entry to the desk). Within the latter case, for instance, one wouldn’t choose buffering.

It is best to, subsequently, choose:

• Buffering isn’t allowed if a desk isn’t buffered.
• Buffering allowed however not activated if buffering is principally allowed for a desk, however in the mean time no buffering needs to be energetic. The buffering kind specified on this case is simply a suggestion.
• Buffering is allowed if the desk needs to be buffered. On this case, a buffering kind have to be specified.

Buffering Sort

The buffering kind defines whether or not and the way the desk needs to be buffered.

There are the next kinds of buffering:

• single-record buffering –> Press F1 for extra particulars
• generic space buffering –> Press F1 for extra particulars
• full buffering –> Press F1 for extra particulars

In generic space buffering, a lot of key fields between 1 and no. of key fields-1 have to be specified.

No. Of Key Fields for Generic Buffers

When you learn a file from a generically buffered desk, all information whose left-justified a part of the important thing corresponds to that of this file (generic key fields) are loaded into the buffer.

This left-justified a part of the secret is decided on this discipline by coming into a quantity n of key fields. The primary n key fields of the desk are thus the generic key fields.

Create Authorization Object

To create an Authorization Object, go to transaction SE54.

Enter the Desk/View identify for which the Authorization object needs to be created.

Choose the Radio Button ‘Authorization teams’.

Then click on on Create/Change.

Then, the following display will give an inventory of Authorization Objects which can be already current within the system. You may Choose one in every of them from the out there listing as per the requirement. But when the desk calls for a brand new authorization object then click on on New Entries pushbutton given on the display.

Enter the brand new authorization object identify and outline as proven within the display beneath. The authorization object should observe a sure naming conference. (It ought to all the time begin with ‘Z’.) Click on on Save.

Desk Upkeep Generator

1. Go to SE12 transaction. Open the desk for which the desk upkeep is to be carried out.
2. Change it to the Editable mode after which click on on Utilities -> Desk upkeep generator.

Enter the next particulars on the following display:

• Authorization group: Assigned/created for the desk by following the process given in Part I.
• Perform group: Identify of the perform group to which the generated upkeep modules will belong.
• Upkeep kind: In response to the desk requirement, anybody needs to be chosen.
  • One step: Just one upkeep display is processed throughout prolonged desk upkeep. The entries are displayed in listing kind on this display.
  • Two step: Two upkeep screens are processed throughout the prolonged desk upkeep:

On the Overview display, the entries are displayed in listing kind.

One entry is displayed on the only display. For each entry, the only display could be referred to as from the overview display by urgent the perform key.

Upkeep Display screen No

In response to the upkeep kind chosen, an summary display and a single display needs to be entered. Recording routine—That is an indicator of the recording routine that needs to be used for the desk contents.

• Normal recording routine
• No, or person, recording routine

Evaluate Flag

This flag signifies whether or not the upkeep transaction permits the (checked) activation of Enterprise Configuration Units (BC Units) and the adjustment. That is the case if the upkeep transaction can run within the background. There are 4 choices current for the evaluate flag:

• No Data
• Not Adjustable
• Adjustable in Dialog
• Routinely Adjustable

As soon as accomplished. Click on on Create.

Exceptions

If adjustments are made to the desk after the era of desk upkeep, desk upkeep ought to be re-generated for the desk.

1. Click on on Utilities -> Desk Upkeep Generator.
2.  Click on on the Edit button. A pop-up would ask for Motive for change. Choose the suitable causes.
3. Then, Save the information.
4. Go to System -> Standing and duplicate the Program Identify.

Altering the Supply Code of Desk Upkeep

If fields like final modified on, final modified by, and many others., are current within the desk, logic needs to be included to save lots of them by the system.

1. Go to transaction SE80 and open this system that was acquired from the above logic.
2. Go to the Screens drop-down listing and click on on 0001. Within the PAI occasion of that display, add a module to incorporate the logic.
3. Double-click on the module. It would ask for the ‘Embrace’ by which this module needs to be included.
4. Choose the Embrace the place we have to embrace the logic.
5.  Enter the logic to replace the desk with the parameters –> individual accountable for making change, timestamp, and many others. It’s as proven beneath:
6. Go to the structure of the display
7. When you click on on the Structure button, the display beneath will seem.
8. Enter the textual content to be displayed because the column heading within the output display.
9. Change the attributes of the fields of the desk which can be required to be non-editable as ‘OUTPUT ONLY’, i.e., the fields LASTCHANGED, CHANGEDATE, and CHANGE_TIME. The Columns will routinely be grayed out and uneditable on the output display.
10. Save and Activate the adjustments.

Create Transaction

1. To create a transaction, go to transaction SE93. Enter the transaction identify which is to be created.
2. Click on on Create.
3. Enter the Brief textual content and the Begin Object and choose Okay.
4. Enter the beneath particulars and the Click on on SAVE
5. Enter the created T-code and the beneath display would seem as output.
6. Click on on the New Entries button to create an entry within the desk. Enter the main points after which click on on SAVE.
7. As quickly as you click on on the save button the username, Date and Time seems routinely.
8. You may examine the identical knowledge within the Se16 transaction for the desk.

Applies To

ECC 6.0, S/4 HANA and BI 3. x and seven.0, 7.2, 7.3, BW on HANA and many others.

To summarize, following the above step, you’ll be able to Create a customized desk, keep the information within the desk by way of SM30, and allow safety authorization on that desk.

Please observe: This weblog is for builders who’re nonetheless utilizing SAP S/4 HANA, ECC, and BW.

I hope I used to be capable of offer you slightly perception into how the you’ll be able to create, keep and add safety on a customized SAP desk.

I’d love to listen to your ideas, suggestions, and questions. Please share the weblog along with your crew members, colleagues, and mates working in SAP, and don’t overlook to love and share the weblog and observe me on DZone Maheshsingh Mony.