Skip to content

x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 1684 views
  • Users 0 members are here
Browse Forums
Announcements
275
topics
39
replies
General Discussion
5k
topics
15k
replies
Sage Data & Analytics
45
topics
107
replies
Sage Enterprise Intelligence
177
topics
467
replies
Sage Intelligence Reporting
115
topics
323
replies
Zach Porter

Looking for description data for Payment Terms, Carrier, Delivery Mode

SUGGESTED
Posted By

Hello community, 

I am trying to add some description data to a customer facing crystal report and noticed I am only pulling the ID/ Code of the certain fields but need to show the full description of what that id/code is. Trying to add the descriptions for certain fields and can't find the tables to pull in.

Looking for the descriptions for:
Payment Term (PTE)
Carrier (BPTNUM)
Delivery Mode (MDL)

Example - 

Delivery Mode gives me the code of the mode and not the description I am looking for.

I found the TABMODELIV for Delivery Mode that had a description but has all the funky translation stuff. Is there not a table that has this data without manipulating through sql?

Parents
  • 0
    SUGGESTED

    The key (assuming you are using SQL logic in your CR) is to use ATEXTRA table to translate

    For payment terms for example the query should look like this

    select PTE_0,AT.TEXTE_0 from PROD.TABPAYTERM T

    LEFT JOIN PROD.ATEXTRA AT ON CODFIC_0 = 'TABPAYTERM' AND T.PTE_0 = IDENT1_0 AND LANGUE_0 = 'ENG'

    CODFIC_0 should represent the source (payment terms) table 

    PTE_0 is the business object you would like to join (differ based on the table)

    and I've hardcoded LANGUE_0 = 'ENG'

    Tip - If you quickly want to see the structure of the ATEXTRA table that only relevant to the join , you can SELECT * from ATEXTRA where TEXTE_0 = <the translated string>

    For example

    SELECT * FROM PROD.ATEXTRA WHERE TEXTE_0 = 'Net 45 Days'

Reply
  • 0
    SUGGESTED

    The key (assuming you are using SQL logic in your CR) is to use ATEXTRA table to translate

    For payment terms for example the query should look like this

    select PTE_0,AT.TEXTE_0 from PROD.TABPAYTERM T

    LEFT JOIN PROD.ATEXTRA AT ON CODFIC_0 = 'TABPAYTERM' AND T.PTE_0 = IDENT1_0 AND LANGUE_0 = 'ENG'

    CODFIC_0 should represent the source (payment terms) table 

    PTE_0 is the business object you would like to join (differ based on the table)

    and I've hardcoded LANGUE_0 = 'ENG'

    Tip - If you quickly want to see the structure of the ATEXTRA table that only relevant to the join , you can SELECT * from ATEXTRA where TEXTE_0 = <the translated string>

    For example

    SELECT * FROM PROD.ATEXTRA WHERE TEXTE_0 = 'Net 45 Days'

Children
No Data

*Community Hub is the new name for Sage City