1. SAP Tutorial
  2. Business Warehouse

BDSLOIO31 SAP table for – BDS: Instances of Logical Information Objects

Here we would like to draw your attention to BDSLOIO31 table in SAP. As we know it is being mainly used with the SAP BW-PLA (Planning in BW) component which is coming under BW module (Business Warehouse). BDSLOIO31 is a SAP standard transp table used for storing BDS: Instances of Logical Information Objects related data in SAP. It comes under the package UPS.

SAP BDSLOIO31 table

Table BDSLOIO31 technical data

TableBDSLOIO31
Data storingBDS: Instances of Logical Information Objects
ModuleBW
Sub ModuleBW-PLA-BPS
SAP PackageUPS
Delivery ClassC – Customer table, data is only maintained by the customer
ComponentSAP_BW
Table CategoryTRANSP

SAP BDSLOIO31 Table Fields

Here is the details of each fields in this SAP table. You can find the discription, data type and assigned lenth of each of the fields in BDSLOIO31 table.

  • MANDT : Client
    Its a key field. Its data type is CLNT (Character with length 3) with field length 3
  • LOIO_ID : Logical document
    Its a key field. Its data type is CHAR (Character String) with field length 32
  • LO_CLASS : Class of logical document
    Its data type is CHAR (Character String) with field length 10
  • .INCLUDE : SDOK: Fields for instances for logical information objects
  • MASTER_LG : Original language
    Its data type is LANG (Language key character with length 1) with field length 1
  • CREA_USER : Created by
    Its data type is CHAR (Character String) with field length 12
  • CREA_TIME : Creation time (UTC)
    Its data type is NUMC (Character String with Digits Only) with field length 14
  • CHNG_USER : Last changed by
    Its data type is CHAR (Character String) with field length 12
  • CHNG_TIME : Time of change (UTC)
    Its data type is NUMC (Character String with Digits Only) with field length 14
  • .INCLUDE : SDOK: Attribute fields in header record for log. info obj.
  • PROP01 : Attribute feature (short version)
    Its data type is CHAR (Character String) with field length 15
  • PROP02 : Attribute feature (short version)
    Its data type is CHAR (Character String) with field length 15
  • PROP03 : Attribute feature (short version)
    Its data type is CHAR (Character String) with field length 15
  • PROP04 : Attribute feature (short version)
    Its data type is CHAR (Character String) with field length 15
  • PROP05 : Attribute feature (mid-length version)
    Its data type is CHAR (Character String) with field length 20
  • PROP06 : Attribute feature (mid-length version)
    Its data type is CHAR (Character String) with field length 20
  • PROP07 : Attribute feature (mid-length version)
    Its data type is CHAR (Character String) with field length 20
  • PROP08 : Attribute feature (long version)
    Its data type is CHAR (Character String) with field length 40
  • PROP09 : Attribute feature (long version)
    Its data type is CHAR (Character String) with field length 40
  • PROP10 : Attribute feature (long version)
    Its data type is CHAR (Character String) with field length 40

    • BDSLOIO31 related tables

    • BDSPHRE31 : BDS: Outgoing Relationships of Physical Information Objects
    • UPS_NAME_RES_T : Text Table for Name Resolve
    • UPS_TP_AREA : Connection Subplan-Area
    • UPS_STATUS_T : Text Table on UPS_STATUS
    • BDSLOPR31 : BDS: Attribute Values of Logical Information Objects
    • UPS_EVENTS : Table for Event Coupling in Planning Session
    • UPS_NAME_RESOLVE : Table of Permitted Applications for Name Resolve
    • BDSRE31 : BDS: Relationship Instances
    • UPS_TEILPLAN_T : Text Table for UPS_TEILPLAN
    • BDSREPR31 : BDS: Relationship Attributes
    • BDSPHRI31 : BDS: Incoming Relationships of Physical Information Objects
    • BDSPHNM31 : BDS: Use of Target Anchors in Physical Objects
    • UPS_VERSION : Versions/Session for Status Tracking
    • BDSPHF31 : BDS: Files of Physical Information Objects
    • UPS_VERSION_T : Text Table for UPS_VERSION
    • UPS_SUBSTITUTE : Table for Substitute Concept
    • BDSCHKF31 : BDS: File Name for Last Check-Out
    • BDS_CONN31 : BDS: Link Table Default for Undefined Classes
    • BDSLORI31 : BDS: Incoming Relationships of Logical Information Objects
    • UPS_LOCKS : Lock Table for Status and Tracking System

    BDSLOIO31 related transaction codes under SAP package UPS

    • BPS_RM : Reminder Report STS
    • BPS_TC : Maintain Status and Tracking System
    • BPS_STS_START : Start STS Execution

    Related References

    Related Tutorials

    BDSLOIO12 SAP table for – BDS: Instances of Logical Information Objects

    BDSLOIO12 table in SAP BW (Planning in BW) module. This table is used for storing data of BDS: Instances of...

    BDSLOIO11 SAP table for – BDS: Instances of Logical Information Objects

    BDSLOIO11 table in SAP BW (Business Explorer in BW) module. This table is used for storing data of BDS: Instances...

    BDSPHIO12 SAP table for – BDS: Instances of Physical Information Objects

    BDSPHIO12 table in SAP BW (Planning in BW) module. This table is used for storing data of BDS: Instances of...

    BDSPHIO31 SAP table for – BDS: Instances of Physical Information Objects

    BDSPHIO31 table in SAP BW (Planning in BW) module. This table is used for storing data of BDS: Instances of...

    BDSPHIO11 SAP table for – BDS: Instances of Physical Information Objects

    BDSPHIO11 table in SAP BW (Business Explorer in BW) module. This table is used for storing data of BDS: Instances...

    BDSLOPR31 SAP table for – BDS: Attribute Values of Logical Information Objects

    BDSLOPR31 table in SAP BW (Planning in BW) module. This table is used for storing data of BDS: Attribute Values...

    BDSLOIO8 SAP table for – BW Metadata: Instances of Logical Information Objects

    BDSLOIO8 table in SAP BW (Warehouse Management in BW) module. This table is used for storing data of BW Metadata:...

    «
    »