Scott's E1 Development Blog

Here is a quick and simple example of how to use the date format string to convert a string to a date. This beats the heck out of parsing the string manually which I have done many many times. In this example I am using "OAE" to decode the date string. The business function is B74I0010.

0001 VA evt_DateStr_DSC1 = "08062011"
0002 Convert String to Date Using Format Mask
       VA evt_DateValue_DATE01 <- BF ConvertedDate
       VA evt_DateStr_DSC1 -> BF StringToConvert
       "OAE" -> BF FormatMask  
0003  VA evt_DateInvoice_DIVJ = VA evt_DateValue_DATE01

I finally found notes on how to construct and how to read the format masks that are used in some string-to-date and date-to-string functions. I have found this information before and always have trouble finding it again. So, I figured I would put it here so I can easily find it next time. Plus, everyone else will get to enjoy the same benefit.

Examples
char szDateOne[ ] = "03/10/1994\n";
char szFormatMask[ ] = "OSASE";

Masks Available
Mask Description
D Day Number, 1 or 2 digits.
A Day Number, ZERO pad to 2 digits.
Y Day Number, space pad to 2 digits.
M Month Number, 1 or 2 digits.
O Month Number, ZERO pad to 2 digits.
N Month Number, space pad to 2 digits.
T Month Number, by language, from UDC.
B Abbreviated Month Name, by language, from UDC.
R 2 Digit Year.
E 4 Digit Year.
S Date slash character, from configuration.
C Date comma character, from configuration.

When using subforms you are not able to enable the standard media object functionality via the form design aid menu. Here is a method you can use to enable the paper clip and to display the default text media object. The example code below is based on the Purchase Order header media object structure. For your code just substitute your media object data structure and parameters in place of the PO Header values I am using.

1st Step: Enable the paper clip
In the Grid Record is Fetched Event add this code.

frm_MediaObject_EV01 = "0"

Media Object Structures(GT4301, < Default Media Object > , < Exist > , 
                        frm_MediaObject_EV01, 
                        BC Document (order No, Invoice, etc.)(F4301), 
                        BC Order Type (F4301), 
                        BC Order Company (Order Number)(F4301), 
                        BC Order Suffix (F4301))

If frm_MediaObject_EV01 is equal to "1"
  Set Grid Text Indicator(FC Commodity Code 01, 
                          < Currently Selected Row > , 
                          < Yes > )
Else
  Set Grid Text Indicator(FC Commodity Code 01, 
                          < Currently Selected Row > , 
                          < No > )
End If

2nd Step: Display the standard media object dialog.
In the Double Click on Row Header Event (for the grid) add this code.

frm_DisplayMediaObject_EV01 = "0"

MMedia Object Structures(GT4301, < Default Media Object > , 
                                 < Display > , 
                                 < First Text Item > , 
                                 VA frm_DisplayMediaObject_EV01, 
                                 GC Order Number, 
                                 GC Or Ty, 
                                 GC Order Co, 
                                 000)

There are some new system functions that until now I have not tried out. Sometimes there is a need to loop through the selected records in a grid instead of all the records in he grid.

In the past we have looped through all of the records in the grid and determined one by one which ones were selected and which ones were not. The new system functions make it much easier to work only with the selected records in a grid.

Get Selected Grid Row Count - Returns how many records have been selected.
Get Selected Grid Row Number - Returns the grid row number of the first selected record.
Get Next Selected Grid Row - Returns the row number of the next selected row.

Sample code:

Get Selected Grid Row Count(FC Grid, VA frm_SelectedCount_LNID)

If VA frm_SelectedCount_LNID is greater than Zero

  Get Selected Grid Row Number(FC Grid, VA frm_GridRowNumber_INT01)

  While VA frm_GridRowNumber_INT01 is greater than Zero

    Get Grid Row(FC Grid, VA frm_GridRowNumber_INT01)

    Get Next Selected Row(FC Grid, VA frm_GridRowNumber_INT01, 
                          VA frm_GridRowNumber_INT01)

  End While
End If

I found some information from Oracle that helps to customize the emailing from XML Publisher a little bit while we wait for the real solution. This is not great, but it's better than nothing.

To Change the subject of the email:
1) Run P92002
2) Modify the glossary text for 951S.

To Change the text in the text attachment:
1) Run P92002
2) Modify the glossary text for 951T.

To Change the from Address change this in the jde.ini file. But, remember this is a global setting affecting all emails sent by the system.

JD Edwards EnterpriseOne XML publisher(BI Publisher) is being adopted fairly quickly as customers are installing tools 8.97 or higher. One of the big things that Oracle has been touting is the ability to email documents to customers, suppliers, and internal employees.

I spent some time at a client where we creating order confirmations, shipment confirmations, etc that they could send to the client. The forms themselves look great. We built them to burst on each customer and then set them up to be emailed.

It looks like this:

The text attachment says this, "Please see attachment for EnterpriseOne Report Definition output."

The PDF attachement is the actual form that was to be sent to the customer.

I think this format is fine for sending reports around the company internally. But, this is a bit too generic to actually send to a customer. What would the customer think if you sent this to them? You can not configure the From, CC, subject, body text, or the text in the text attachement.

Isn't this just silly? I don't think they really thought this part out before giving us this feature. They have opened a couple of bug reports to add these features to the email capability. It is "BUG:8788154 - XMLP EMAIL DELIVERY ENHANCEMEN" and "Bug:8929426" It's current status is Pending Review. You can look it up on metalink3.

Until Oracle adds the ability to customize these parameters I don't think it's ready for prime time. If enough customers complain they have to fix it. Enter your service request today to help us get this fixed.

I have been working with the new Requisition self-service module from JDE. They added a new system code 43E. I was doing some custom development for this module when I ran into an issue.

I was following the standard JDE naming convention for creating a table. For example, I created a new table F5543E01. The default business view name should be V5543E01A. This business view name is 9 characters long. It shouldn't be a problem. The OMW truncated it and displayed a message that explained that the business view name could only be 8 characters. This causes a problem for me when trying to adhere standard naming conventions.

I looked at the C function and noticed that they had changed the code that checks this object name length. They just changed it awhile ago. The only reason it has been noticed now is due to the new 3 character jde codes they have added recently. I filed a service request with Oracle to fix this if possible. Apparently they had made the change because of file name size limitations on the AS400. If you are running windows servers the limitation does not apply.

They created bug 8921650. The status is "Pending Review". UGH!!

2 ways around the issue:
1)If you can keep table names to 7 characters max then you can still use the standard naming convention for the associated business view.
2)You can modify the underlying business function that checks the length of the object name to allow business views to have more than 8 characters. If you are not running with an AS400 server you can make this change without affecting anything.

This will be the first of regular entries into this blog. I will attempt to log advice, issues, or new things I learn in E1 that will be helpful to others.