Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Oss note - 870277

Go to solution
Former Member

‎2007 Dec 03 4:22 PM

0 Likes
676

Hi ,

To implement the oss note - 870277, what are the manual corrections need s to be done.

My version is 4.6C, and support package is 46c45.

I had already gone through the manual corrections that needs to be done, However before implemnting i wanted to confirm this.

Please check.

1 ACCEPTED SOLUTION
Read only

Go to solution
Former Member

‎2007 Dec 03 4:38 PM

0 Likes
592

Hi,

When I look into the Note I found following manual opertions to be carried out, so chk these steps.

Import the Support Package specified for your release, or implement this note in advance.

To implement this note, carry out the following manual tasks:

1. Create the following data elements (Transaction SE11):

Data element ASLMMONA

Short description EC sales list: Reporting Period

Package FREP

Domain NUMC2

Field label Reporting Period

Data element ASLMPERTYP

Short description EC sales list: Period type

Package FREP

Domain CHAR1

Field label Period type

Save and activate the data elements.

2. Add two new fields to the end of data structures ASL_PARAM and ASLM (Transaction SE11):

Component MONAT

Component type ASLMMONA

and

Component PERTYP

Component type ASLMPERTYP

Save and activate the structures.

The ASL_PARAM structure only exists as of Release 4.6C. Carry out this action in lower releases (3.1I up to 4.6B) for the ASLM structure only.

3. Create new message texts (Transaction SE91):

Message class FR

Number 540

Short text 'You cannot specify month and quarter simultaneously'

Self-explanatory X

Message class FR

Number 541

Short text 'Specification of reporting month (1 to 12) incorrect'

Self-explanatory X

Message class FR

Number 542

Short text 'Enter year of reporting month'

Self-explanatory X

This is only valid for Release 4.6C and higher. In Releases 3.1I to 4.6B, use the message numbers 590, 591 and 592 instead of the message numbers 540, 541 and 542.

4. Implement the program corrections using the attached correction instructions.

5. Create or change the following text symbols (Transaction SE38):

Report RFASLD20 (only for Release 4.6C and higher)

Text symbol 012

Text 'Reporting Period'

Max. length 30

Report RFASLD02

Text symbol 012

Text 'Reporting Period'

Max. length 30

Report RFASLM00

Text symbol 012

Text 'Reporting Period'

Max. length 30

Report RFASLM00

Text symbol 003

Text 'EC sales list for the month Y'

Max. length 30

Report RFASLM00

Text symbol 908 (change)

Text '|The reporting quarter or the reporting month is not specified on the data carrier or the message|'

Max. length 132

Save and activate the text elements.

I hope this will help you.

Regards,

Amey

Hi ,

To implement the oss note - 870277, what are the manual corrections need s to be done.

My version is 4.6C, and support package is 46c45.

I had already gone through the manual corrections that needs to be done, However before implemnting i wanted to confirm this.

Please check.

Reply
2 REPLIES 2
Read only

Go to solution
Former Member

‎2007 Dec 03 4:38 PM

0 Likes
593

Hi,

When I look into the Note I found following manual opertions to be carried out, so chk these steps.

Import the Support Package specified for your release, or implement this note in advance.

To implement this note, carry out the following manual tasks:

1. Create the following data elements (Transaction SE11):

Data element ASLMMONA

Short description EC sales list: Reporting Period

Package FREP

Domain NUMC2

Field label Reporting Period

Data element ASLMPERTYP

Short description EC sales list: Period type

Package FREP

Domain CHAR1

Field label Period type

Save and activate the data elements.

2. Add two new fields to the end of data structures ASL_PARAM and ASLM (Transaction SE11):

Component MONAT

Component type ASLMMONA

and

Component PERTYP

Component type ASLMPERTYP

Save and activate the structures.

The ASL_PARAM structure only exists as of Release 4.6C. Carry out this action in lower releases (3.1I up to 4.6B) for the ASLM structure only.

3. Create new message texts (Transaction SE91):

Message class FR

Number 540

Short text 'You cannot specify month and quarter simultaneously'

Self-explanatory X

Message class FR

Number 541

Short text 'Specification of reporting month (1 to 12) incorrect'

Self-explanatory X

Message class FR

Number 542

Short text 'Enter year of reporting month'

Self-explanatory X

This is only valid for Release 4.6C and higher. In Releases 3.1I to 4.6B, use the message numbers 590, 591 and 592 instead of the message numbers 540, 541 and 542.

4. Implement the program corrections using the attached correction instructions.

5. Create or change the following text symbols (Transaction SE38):

Report RFASLD20 (only for Release 4.6C and higher)

Text symbol 012

Text 'Reporting Period'

Max. length 30

Report RFASLD02

Text symbol 012

Text 'Reporting Period'

Max. length 30

Report RFASLM00

Text symbol 012

Text 'Reporting Period'

Max. length 30

Report RFASLM00

Text symbol 003

Text 'EC sales list for the month Y'

Max. length 30

Report RFASLM00

Text symbol 908 (change)

Text '|The reporting quarter or the reporting month is not specified on the data carrier or the message|'

Max. length 132

Save and activate the text elements.

I hope this will help you.

Regards,

Amey

Read only

Go to solution
Former Member
In response to Former Member

‎2007 Dec 04 6:19 AM

0 Likes
592

thank you Amey!!

but i wanted in the pre-requisite notes!

am pretty much confident on the oss note 870277!!

pls help!!