Mar 18, 2014 Get to know your time with your computer. Keygen sap r3 license and object key generator v1.70.exe 2. Preempted up with fun ideas for a closed respiratory-wackiness everglades. Keygen sap r3 license and object key generator v1.70.exe 2.
Here we would like to draw your attention to MASE table in SAP. As we know it is being mainly used with the SAP LO-MD (Logistics Basic Data in LO) component which is coming under LO module (Logistics). MASE is a SAP standard transparent table used for storing Last Serial Number for Material related data in SAP. It comes under the package IQSM.
Table MASE technical data
Table | MASE |
Data storing | Last Serial Number for Material |
Module | LO |
Component | LO-MD |
SAP Package | IQSM |
Delivery Class | A – Application table (master and transaction data) |
Table Category | TRANSPARENT |
SAP MASE Table Fields
Here is the details of each fields in this table.You can find the discription, data type and assigned lenth of each of the fields in MASE table.
Its a key field. Its data type is C (Character String) with field length 18
MASE related tables
- EQBS : Serial Number Stock Segment
- SER09 : Doc. Header for Serial Numbers for Purchase Requisition Item
- T377G : Criteria for Serial Number Management (Group)
- T377P : Serial Number Management Profiles
- SER05 : Document Header for Serial Numbers for PP Order
- OBJK : Plant Maintenance Object List
- SER00 : General Header Table for Serial Number Management
- SERI : Serial Numbers
- SER07 : Document Header for Serial Numbers in Physical Inventory
- T377X : Documents Allowed for Serial Number Management
- SERBL : Plant Maintenance Object List
- EQSE : Serial Number Records
- ARC_PM_OBJLIST : Customizing for Archiving of Serial Number Object Lists
- T377 : Criteria for Material Serial Number Management
- SER01 : Document Header for Serial Numbers for Delivery
- SER04 : Document Header for Serial Numbers for Inspection Lot
- ARC_PM_OBJLIST_T : Customizing Texts for Archiving of Serial Number History
- T377P_T : Texts for Serial Number Management Profiles
- SER02 : Document Header for Serial Nos for Maint.Contract (SD Order)
- SER06 : Document Header for Serial Numbers for Handling Unit-Content
Related References
Keygen Repository Entries
Table: SMO9_XFTCH
Field Name | Field Type | Remarks |
SR_NO | Integer | Serial Number that gives the order of filling of fields belonging to the same transaction. |
TRANS_ID | Character(32) | The Transaction ID of the transaction. |
DEST_TABLE | Character(30) | The Table of the currently processed Segment. |
DEST_FIELD | Character(30) | The Field of the currently processed Segment where the entry is to be written. |
SRC_TABLE | Character(30) | The Table from which the Extra Fetch Field is to be picked up. |
SRC_FIELD | Character(30) | The Field from which the Extra Fetch Value is to be picked up. |
CONC_PFLDS | Character(255) | The Fields of the Source Table used to make the Where Clause for Select statement into CDB. |
CONC_PDEST | Character(255) | The Fields of the Destination Table used to make the Where Clause for Select statement into CDB. |
FETCHOPT | Character(1) | The Fetch Option specifies the options on which a field is to be fetched – M – Fetch only if Destination is Empty E – Fetch only if Source is Non-Empty O- Fetch & Overwrite |
DEST_COND | Character(255) | The Destination Condition used to specify the condition clause to be satisfied for fetching. This condition will be applicable in the Destination Segment. '<FLDNAME> <operator> <Value>' |
SRC_COND | Character(255) | The Source Condition used to specify the condition clause to be satisfied for fetching. This condition will be applicable in the Source Table. '<FLDNAME> <operator> <Value>' This will be used as an extra Where clause field. |
INACTIVE | Character(1) | This flag indicates whether the entry in the table is active or not. |
Use
The SMO9_XFTCH table has the following uses:
- Keygen is generated specific to a BDoc type.
- For a Keygen generated code, all the SMO9_XFTCH entries corresponding to the BDoc type are processed. The field TRANS_ID is used as the filtering field to select all such entries.
- The field SR_NO is used to identify the order of filling the SMO9_XFTCH entries.
- It is identified whether the SRC_FIELD entry is the name of the primary key of the table in SRC_TABLE. If so, a search in the Key table is allowed.
- The aim is to find the field’s value from various sources, and fill the value in the segment structure of the BDoc type that corresponds to the DEST_TABLE. The field where it will be filled in is the DEST_FIELD.
- The fields TRANS_ID and DEST_TABLE together identify a segment of the BDoc type and the fields TRANS_ID, DEST_TABLE and DEST_FIELD together identify the segment field of the segment in the BDoc type.
- The field values of CONC_PFLDS and CONC_PDEST are a set of fields used to filter out the fetch value. Hence these fields are used to form the WHERE clause. They are to be entered in a concatenated form each field name, separated by ‘+’.
- In case the SRC_FIELD is a primary key of the table SRC_TABLE and a Key Table search is necessary, then:
- CONC_PFLDS should contain a list of R/3 key (or CRM key) field names of segment mapped to SRC_TABLE.
- This list should follow the order TR_POS in transaction repository table SMOG_SFLD for the segment mapped to SRC_TABLE.
- CONC_PDEST should contain a list of field names corresponding to the CONC_PFLDS, but those that exist in the segment mapped to DEST_TABLE.
- This list should follow the same order of fields as given in CONC_PFLDS.
- The fields in CONC_PFLDS are used to form the WHERE Clause field names and the fields in CONC_PDEST are used to form the values to the WHERE clause field names.
- In case the SRC_TABLE value belongs to one of the mapped tables of the BDoc type, then the following case applies:
- The fields TRANS_ID and SRC_TABLE together identify a segment of the BDoc type and the fields TRANS_ID, SRC_TABLE and SRC_FIELD together identify the segment field of the segment in BDoc type.
- In general, the following sequence of Search is done. Some of the searches will not be available in certain cases
- Search for value in the segment of SRC_TABLE in segment field of SRC_FIELD. If not found, proceed to the next search.
- In case, SRC_FIELD is the primary key of the SRC_TABLE, search for value in an internal table of Key Table. If not found, proceed to the next search.
- In case, SRC_FIELD is the primary key of the SRC_TABLE, search for value in Key Table. If not found, proceed to the next search.
- Search SRC_FIELD in SRC_TABLE (CDB table search). If not found, proceed to the next search.
- If the SRC_TABLE value is not that of a table mapped as a segment to the BDoc type, then the search in segment data of SRC_TABLE is unavailable.
- If the SRC_FIELD value is not that of a primary key of the SRC_TABLE value, then the search in internal table of Key Table and the Key Table itself is unavailable.
- The DEST_COND is used as a condition to be satisfied before the filling of the value takes place. All the entries of the BDoc type’s data of segment mapped to DEST_TABLE, which satisfy the condition specified, will be filled with the value.
- The SRC_COND is of type: '<FLDNAME> <operator> <Value>'. The SRC_COND is used as a condition applicable on the SRC_TABLE. This extra filter is made available to extract only those CDB table entries, which satisfy it. This condition is added as an extra filter in the WHERE clause. In case, a Key Table search is used, one should make sure that the <FLD_NAME> should be one of the R/3 keys (or CRM keys) of the SRC_TABLE.
- Special Case: When a search of Key Table is necessary and a SRC_COND needs to be given, the following steps could be done:
- The SRC_COND should involve the last R/3 key (or CRM key) of the SRC_TABLE in the order of TR_POS, in the transaction repository table SMOG_SFLD.
- It is also necessary that CONC_PFLDS does not contain the same field used in SRC_COND as one of the filter fields. It is automatically taken from SRC_COND while searching in CDB.
- This case is useful while trying to fill a child segment MSA key in the parent segment and when the parent segment does not contain all the R/3 Key (or CRM key) fields of the child segment. Hence the R/3 key field (or CRM key) that is missing in the Parent segment and its filter value are given as source conditions.