CopyCallMediaObject

CopyCaseMediaObject

Minor Business Rule

Object Name: B1700450

Parent DLL: CCRIN

Location: Client/Server

Language: C

1.Functional Description
This function copies the media object text and attachments from the Call Media Object (GT1755) to the Message Media Object (GT01131).

1.1Purpose
This function copies the media object text and attachments from the Generic text Table (F00165) for the Call Media Object (GT1755) to the Message
Media Object (GT01131).

1.2Setup Notes and Prerequisites
This function expects the media object text to exist in the Generic Text table(F00165).  This function should be run on an event that occurs after the
database has been updated.  The actual attachment is not copied.  Only the reference to the attachment is stored with the media object.  Only these
references to attachments will be copied.

1.3Special Logic
This function uses the CopyGenericTextName API to copy the text and attachments.
When calling this function you must either send the call number, type, and company or the request number.
If the request number is sent the function will copy from the E Request media object GT1761.  If the call number, type and company are sent the
function will copy from the Call media object GT1755.

Data Structure

D1700450 - Copy Case Media Object

Parameter Name Data Item Data Type Req/Opt I/O/Both

mnCallNumber DOCO MATH_NUMERIC REQ INPUT

A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on.

szCallDocumentType DCTO char REQ INPUT

A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and
should not be changed: P Accounts Payable documents   R Accounts Receivable documents   T Payroll documents   I Inventory documents
O Purchase Order Processing documents   J General Accounting/Joint Interest Billing documents   S Sales Order Processing documents

szCallCompanyKey KCOO char REQ INPUT

A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a
sales order, and so on). If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the
order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order
type, the order company lets you locate the desired document. If you use the regular Next Numbers facility, the order company is not used to
assign a next number. In this case, you probably would not use the order company to locate the document.

mnKeyValueSerialNumber SERK MATH_NUMERIC REQ INPUT

A key identification number used internally to identify a composite key structure.  The actual key items must be stored in another file and
given this serial number.  This is to avoid repeating a very large key structure with repeating data items.

mnTaskNumber RCK7 MATH_NUMERIC OPT NONE

This field is used to create a unique key within a file.  If you are using a program which will allow you to resequence the records, we
recommend you use one of the following data dictionary items:  DSS5, DSS7, DSS9.

Related Functions

None

Related Tables

F01131 PPAT Message Control File

F1755 Case Master

F1757 Task Master

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnCallNumber	DOCO	MATH_NUMERIC	REQ	INPUT
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry, and so on.
szCallDocumentType	DCTO	char	REQ	INPUT
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and should not be changed: P Accounts Payable documents R Accounts Receivable documents T Payroll documents I Inventory documents O Purchase Order Processing documents J General Accounting/Joint Interest Billing documents S Sales Order Processing documents
szCallCompanyKey	KCOO	char	REQ	INPUT
A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a sales order, and so on). If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order type, the order company lets you locate the desired document. If you use the regular Next Numbers facility, the order company is not used to assign a next number. In this case, you probably would not use the order company to locate the document.
mnKeyValueSerialNumber	SERK	MATH_NUMERIC	REQ	INPUT
A key identification number used internally to identify a composite key structure. The actual key items must be stored in another file and given this serial number. This is to avoid repeating a very large key structure with repeating data items.
mnTaskNumber	RCK7	MATH_NUMERIC	OPT	NONE
This field is used to create a unique key within a file. If you are using a program which will allow you to resequence the records, we recommend you use one of the following data dictionary items: DSS5, DSS7, DSS9.

F01131 PPAT Message Control File
F1755 Case Master
F1757 Task Master