SAP implementation of RFC 1738

Question

When looking over the ABAP implementation of RFC 1738 (don't ask) I noticed that SAP marks the following characters as unsafe and as a result URL encodes them:
"<, >, “, #, %, {, }, |, \, ^, ~, [, ], `" and ";, /, ?, :, @, =, &" (the ABAP code makes no distinction between the character set types of unsafe and reserved in its validation buffer, but I've separated them for clarity.)
The code also URL encodes characters LE 0x1F and GE 7F. This seems mostly correct, but it appears to be missing coma and $ which are both a part of RFC 1738 (to the best of my knowledge). I was unable to find a technote on this, but wanted to solicit some feedback on why this might be the case. Am I missing something, or does the SAP implementation of this standard appear to be slightly off? Any thoughts the development community has on this would be greatly appreciated.
Edit:
Just to clarify I'm specifically refering to the translate subroutine code in the program SAPLSCMS_URL. It defines the following as unsafe:
unsafe(23) value ' <>"#%{}|\^~[]`;/?:@=&+'.
These include all of the unsafe and reserved characters except for , and $.
Message was edited by:
        Aaron Jack

Answer 1

The below table will give you an idea about the deadline for your organization for Chile eDocument implementation -
Enterprise
Last year's
revenue (in UF*)
Last year's
revenue (in USD)
Location
Months (from
Feb, 2014)
Deadline to implement
Chile eDocument
Small
Below 2400
Below 100 K
Urban
24
1st Feb, 2016
Rural
36
1st Feb, 2017
Medium
Between 2400
and 100,000
100 K - 4.2 M
Urban
18
1st August, 2015
Rural
24
1st Feb, 2016
Large
Above 100,000
Above 4.2 M
All
9
1st Nov, 2014
*UF = Unidad de Fomento
1
UF
41.56
USD
as of 23rd Oct, 2014
2400
UF
99744
USD
100,000
UF
4156000
USD