Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
S3 Interfaces/Conversion
Customer Comment Conversion (ARICOMMENT)?
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Joyce
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5158
People Online:
Visitors:
11
Members:
0
Total:
11
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Interfaces/Conversion
Customer Comment Conversion (ARICOMMENT)?
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Garth Gerwing
Basic Member
Posts: 27
7/5/2011 3:20 PM
I see that Lawson has provided a staging table to support comment conversion (ARICOMMENT - consumed by AR506) - and that by leaving the "transaction/invoice-related" elements blank, the process will interpret these comments as "Customer" comments. However:
- there are appears to be no on-line dialogue to support conversion corrections (as per other conversion constructs)
- the ARICOMMENT table has a single "Comment" element of 40 CHARS (which is less apace than desired)
Does anyone have any experience with converting comments through these constructs?
- How would you go about converting a comment that is larger than 40 chars?......or
- How would you go about actively populating the Attachments Title/Text?
John Henley
Senior Member
Posts: 3348
7/5/2011 4:01 PM
I believe you can use the SEQ-NBR field to add multiple 40-character comments.
Ragu Raghavan
Veteran Member
Posts: 468
7/5/2011 4:18 PM
I have not done this, but from what I see in the code, if the keys are the same, it appends,
02 ARCMTWS-PREV-KEYS.
03 ARCMTWS-PREV-COMPANY PIC 9(04) VALUE ZEROES.
03 ARCMTWS-PREV-CUSTOMER PIC X(09) VALUE SPACES.
03 ARCMTWS-PREV-TRANS-TYPE PIC X(01) VALUE SPACES.
03 ARCMTWS-PREV-INVOICE PIC X(22) VALUE SPACES.
03 ARCMTWS-PREV-CMMT-TYPE PIC X(01) VALUE SPACES.
03 ARCMTWS-PREV-BEG-DATE PIC 9(08) VALUE ZEROES.
03 ARCMTWS-PREV-END-DATE PIC 9(08) VALUE ZEROES.
03 ARCMTWS-PREV-SYS-DATE PIC 9(08) VALUE ZEROES.
03 ARCMTWS-PREV-SYS-TIME PIC 9(06) VALUE ZEROES.
03 ARCMTWS-PREV-PRINT-CODE PIC X(01) VALUE SPACES.
* INPUT/OUTPUT:
* FUNCTION CODES FOR ARI1F1:
*
* A = ADD ARCOMMENT AND ATTACHMENT
* B =
* C =
* C =
* D =
* E = APPEND ATTACHMENT
* F =
* G =
* H =
*
******************************************************************
700-CONVERT-ARCOMMENT-80 SECTION.
******************************************************************
700-START.
IF (ARCMTWS-FC = SPACES)
IF (ARCMTWS-COMP-KEYS NOT = ARCMTWS-PREV-KEYS)
MOVE "A" TO ARI1F1-FC
ELSE
MOVE "E" TO ARI1F1-FC
END-IF
You are not authorized to post a reply.