tableAdministration & Setupofficial - Microsoftderived - from the source, no model text

Table 47078 "SL PJProj Buffer"

HybridSL · Microsoft.DataMigration.SL

Across versions

  1. BC23-28not present
  2. BC29-30present

HybridSL · Microsoft.DataMigration.SL · captioned “SL PJProj” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption SL PJProj
Access Internal
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 alloc_method_cd Text[4] —
2 alloc_method2_cd Text[4] —
3 BaseCuryId Text[4] —
4 bf_values_switch Text[1] —
5 billcuryfixedrate Decimal —
6 billcuryid Text[4] —
7 billing_setup Text[1] —
8 billratetypeid Text[6] —
9 budget_type Text[1] —
10 budget_version Text[2] —
11 contract Text[16] —
12 contract_type Text[4] —
13 CpnyId Text[10] —
14 crtd_datetime DateTime —
15 crtd_prog Text[8] —
16 crtd_user Text[10] —
17 CuryId Text[4] —
18 CuryRateType Text[6] —
19 customer Text[15] —
20 end_date Date —
21 EndDateChk Integer —
22 gl_subacct Text[24] —
23 labor_gl_acct Text[10] —
24 lupd_datetime DateTime —
25 lupd_prog Text[8] —
26 lupd_user Text[10] —
27 manager1 Text[10] —
28 manager2 Text[10] —
29 MSPData Text[50] —
30 MSPInterface Text[1] —
31 MSPProj_ID Integer —
32 noteid Integer —
33 opportunityID Text[36] —
34 pm_id01 Text[30] —
35 pm_id02 Text[30] —
36 pm_id03 Text[16] —
37 pm_id04 Text[16] —
38 pm_id05 Text[4] —
39 pm_id06 Decimal —
40 pm_id07 Decimal —
41 pm_id08 Date —
42 pm_id09 Date —
43 pm_id10 Integer —
44 pm_id31 Text[30] —
45 pm_id32 Text[30] —
46 pm_id33 Text[20] —
47 pm_id34 Text[20] —
48 pm_id35 Text[10] —
49 pm_id36 Text[10] —
50 pm_id37 Text[4] —
51 pm_id38 Decimal —
52 pm_id39 Date —
53 pm_id40 Integer —
54 probability Integer —
55 ProjCuryId Text[4] —
56 ProjCuryRateType Text[6] —
57 ProjCuryBudEffDate Date —
58 ProjCuryBudMultiDiv Text[1] —
59 ProjCuryBudRate Decimal —
60 ProjCuryRevenueRec Text[1] —
61 project Text[16] —
62 project_desc Text[60] —
63 purchase_order_num Text[20] —
64 rate_table_id Text[4] —
65 S4Future01 Text[30] —
66 S4Future02 Text[30] —
67 S4Future03 Decimal —
68 S4Future04 Decimal —
69 S4Future05 Decimal —
70 S4Future06 Decimal —
71 S4Future07 Date —
72 S4Future08 Date —
73 S4Future09 Integer —
74 S4Future10 Integer —
75 S4Future11 Text[10] —
76 S4Future12 Text[10] —
77 shiptoid Text[10] —
78 slsperid Text[10] —
79 start_date Date —
80 status_08 Text[1] —
81 status_09 Text[1] —
82 status_10 Text[1] —
83 status_11 Text[1] —
84 status_12 Text[1] —
85 status_13 Text[1] —
86 status_14 Text[1] —
87 status_15 Text[1] —
88 status_16 Text[1] —
89 status_17 Text[1] —
90 status_18 Text[1] —
91 status_19 Text[1] —
92 status_20 Text[1] —
93 status_ap Text[1] —
94 status_ar Text[1] —
95 status_gl Text[1] —
96 status_in Text[1] —
97 status_lb Text[1] —
98 status_pa Text[1] —
99 status_po Text[1] —
100 user1 Text[30] —
101 user2 Text[30] —
102 user3 Decimal —
103 user4 Decimal —

Keys

  • PK: project (clustered)

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "SL PJProj Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources