File layout could be used for bulk uploading of data from other third party
systems to PeopleSoft systems, you know typically there will be no high
level validation is like one of the disadvantage. you can achieve the
integration of file lay out through application engine as well SQR also.
But, as per my knowledge, using file layout is couldn't be a better choice
rather than using a Component Interface. CI is could be preferred because
it provides a high level business validation.
- File layout is a proprietor tool(peoplesoft object),it does the system
validations like translate values,prompt values ,yes or no values ,required
values and boolean values .This is the advantage of file layout .
- The file layout is does not do the business validations like deptid and
effdt and age fileds validations etc,.(its related to people code). This is
the disadvantage of file layout.
Example:I have found one disadvantage to the file layout and there maybe a way to work around this, but I did not find one. We receive a file from an external application and they were sending us data that was longer than the delivered field length for say address1 field, which I believe is 50 chars, and sometimes we would get over 50 chars and it was causing the AE program to fail, it was not truncating the data but failing, I was having to login in the middle of the night and either fix the data, delete the record so that we could import the file and process the data. I finally wrote a SQR to read in the file before hand and correct any field length issues and write out a new file that was read in by the AE using file layout. Not the most desired thing to do, but when people were putting in crazy stuff in the address1 field, what are you going to do, if they can't figure that out, I can't figure it out for them.
FL doesn't have any security layer to access database exither to read or
load . But CI has that security layer for both read and load, at the same
time Business validations can be triggered automatically from CI, no
additional code required to this just invoke CI, But any specific
a validation you need to do i n FL , you need to write the code accordingly
systems to PeopleSoft systems, you know typically there will be no high
level validation is like one of the disadvantage. you can achieve the
integration of file lay out through application engine as well SQR also.
But, as per my knowledge, using file layout is couldn't be a better choice
rather than using a Component Interface. CI is could be preferred because
it provides a high level business validation.
- File layout is a proprietor tool(peoplesoft object),it does the system
validations like translate values,prompt values ,yes or no values ,required
values and boolean values .This is the advantage of file layout .
- The file layout is does not do the business validations like deptid and
effdt and age fileds validations etc,.(its related to people code). This is
the disadvantage of file layout.
Example:I have found one disadvantage to the file layout and there maybe a way to work around this, but I did not find one. We receive a file from an external application and they were sending us data that was longer than the delivered field length for say address1 field, which I believe is 50 chars, and sometimes we would get over 50 chars and it was causing the AE program to fail, it was not truncating the data but failing, I was having to login in the middle of the night and either fix the data, delete the record so that we could import the file and process the data. I finally wrote a SQR to read in the file before hand and correct any field length issues and write out a new file that was read in by the AE using file layout. Not the most desired thing to do, but when people were putting in crazy stuff in the address1 field, what are you going to do, if they can't figure that out, I can't figure it out for them.
FL doesn't have any security layer to access database exither to read or
load . But CI has that security layer for both read and load, at the same
time Business validations can be triggered automatically from CI, no
additional code required to this just invoke CI, But any specific
a validation you need to do i n FL , you need to write the code accordingly
No comments:
Post a Comment