Incorrect Condition Values when billing multiple deliveries

Hi all.
Ok this is a new one on me, when i bill using VF01 and enter multiple deliveries in (2) then second billing document (2 are created) that is created has some condition values that differ from the first, i must add it the same material, condition values, qty and ship to on the deliveries, also the deliveries are NOT reference to a sales order.
But when you create each delivery as a single billing document all is ok.
Any initial ideas?
Just better add this is a density calulation as we use the F&A pricing for these billing docs.
Regards
Steve
Edited by: Steve Cane on Mar 31, 2009 10:16 AM

Hello steve,
some possibilities
some of the conditions may be group conditions and hence the base is the cumulative of both the conditions
copy control from delivery to invoice may be to redtermine the scales and hence it may be updating when together
hope this helps
Thanks
akasha

Similar Messages

Condition value in billing not coming properly.

Hi All,
We have an issue wherein the condition value in billing document is not coming properly.
When qty is multiplied by the price the value should come as 208.04 ( 54.51 * 4 qty ), but the condition value is coming as 16.77.
We checked but could not find any proper reason for this.
When checked in details of condition type, we can see the Condition Origin as manually entered, but we are ot ale to trace the changes and also who entered the condition manually.
Kindly advise on the issue as it

Hi Mr. Satish,
I agree with Mr. Rajesh and for your 2nd question.
We can easily track down who entered the condition type in order
there are two possiblities
Either user who created the order, enter that condition type, that will not recorded in the changes so you can see the user id at header level--> on sales data page "Created by"
If some other user come in VA02 and enter the condition type then you can see it in
Go to Menu "Enviroment" --> Click at changes --> your document number is there --> Execute and see who entered it
Regards
MT

Referencing condition values when creating return order is wrong...

Hello Experts,
Lets say I have a billing document that has 3 line items namely material A, B and C.
Now, I created a return order for material A with 2 separate line items because of different
storage locations. Now, is there a user-exit that lets my 2nd line item copy the condition values of the
1st line item of the reference billing document? because they are of the same material(A).
Currently, we are having problems when creating a return order having multiple line items of the same material
because the succeeding line items copies the wrong condition values of the referenced billing doc.
For example:
Original billing document:
Material      Discount
A          100
B          200
C          300
Return Order:
Material     Discount
A          100
A          200
A          300
The succeeding line items of my return order must point to the first line item since they are of the
same material. Hope you can help me guys. Thank you and take care!

You may need to explore in the copy control definition, especially the pricing type defined. Check if any customized requirements exists for condition which checks w.r.t to the document number instead of reference document number item.

Wrong pricing condition values when using GN_INVOICE_CREATE

Hi all,
I am currently handling a program where I have to display all the materials in a given sales area and some corresponding values that depend on pricing conditions. I am using FM GN_INVOICE_CREATE to extract table komv. However, I am experiencing a problem because the values I am getting are different from those in table konv. I am getting the price conditions without the value of field KNUMV.
I would like to ask if anybody has any idea on how to go about this or maybe another function module that I can use to get the data I need.
Thanks a lot..
Regards,
jac

Hi,
Thanks for your reply. I only have the field AUART for checking on the pricing conditions.
Here is a the part of my code
CALL FUNCTION 'GN_INVOICE_CREATE'
       EXPORTING
            vbsk_i           = i_vbsk
            id_kvorg        = ''
            id_no_dialog = c_exis
            invoice_date = p_datum
            pricing_date = p_datum
       IMPORTING
            vbsk_e          = i_vbsk
       TABLES
            xkomfk         = i_komfk
            xkomfkgn      = i_komfkgn
            xkomfkko      = i_komfkko
            xkomv          = i_komv
            xthead         = i_thead
            xvbfs           = i_vbfs
            xvbpa          = i_vbpa
            xvbrk           = i_vbrk
            xvbrp           = i_vbrp
            xvbss          = i_vbss
       EXCEPTIONS
            OTHERS       = 1.
The only parameters in those that have values are c_exis = X, p_datum = given date, and xkomfkgn. The other parameters are all initial when passed to the function module. I get a resulting komv table however, values are incorrect.
Thanks again for the help..
Regards,
jac

Incorrect Sender value when 'mail' attribute is multivalued

hi,
i've just upgraded Sun messaging server 2005Q4 from IMS 5.2 and noted some behavioural difference in the reverse_url operations.
I've noted that reverse_url operations on the 'mail' attribute for ims5.2 seems to ignore subsequent values of this attribute if it's multivalued.
Sun Messaging 2005Q4, however, seems to have taken into account the multiple values of the 'mail' attribute.
This is resulting the mail's "From:" field to be using the subsequent values.
Setup
Account: mailtes1 (with multivalued 'mail' attribute)
mail: [email protected]
[email protected] (Not a configured mail domain handled by Sun messaging. Used by other applications)
mailhost: mailsit.portnet.com.sg (for Sun messaging 2005q4)
pnsasit1app1.portnet.com (for ims52)
test mails are sent to the same accounts.
Results of ./imsimta test -rewrite -debug mailtes1 on Sun Messaging 2005q4 as follows:
*** Debug output from rewriting a forward header address:
00:07:53.03: Rewriting: Mbox = "mailtes1", host = "portnet.com.sg", domain = "$*", literal = "", tag = ""
00:07:53.03: Rewrite: "$*", position 0, hash table -
00:07:53.03: Found: "$E$F$U%[email protected]$V$H"
00:07:53.03: Rewrite failed, not envelope.
00:07:53.03: Rewrite: "$*", position 1, hash table -
00:07:53.03: Failed.
00:07:53.03: Rewrite: "$*", position 0, rewrite database -
00:07:53.03: Failed
00:07:53.03: Rewriting: Mbox = "mailtes1", host = "portnet", domain = "portnet.com.sg", literal = "", tag = ""
00:07:53.03: Rewrite: "portnet.com.sg", position 0, hash table -
00:07:53.03: Found: "$U%[email protected]"
00:07:53.03: New mailbox: "mailtes1".
00:07:53.03: New host: "portnet.com.sg".
00:07:53.03: New route: "png1app1-mail.portnet.com.sg".
00:07:53.03: New channel system: "png1app1-mail.portnet.com.sg".
00:07:53.03: Looking up host "png1app1-mail.portnet.com.sg".
00:07:53.03: - found on channel l
00:07:53.03: Routelocal flag set; scanning for % and !
00:07:53.03: Rewrite rules result: [email protected]
00:07:53.03: Checking reverse URL cache for: [email protected]
00:07:53.03: Applying reverse URL pattern ldap:///$V?mail?sub?$Q to: [email protected]
00:07:53.05: Resulting URL: ldap:///l%3DSGSIN%2Co%3Dportnet.com?mail?sub?(|([email protected])([email protected]))
00:07:53.05: mmc_open_url called to open ldap:///l%3DSGSIN%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg)), flags = 384
00:07:53.05: URL with quotes stripped: ldap:///l%3DSGSIN%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg))
00:07:53.05: LDAP URL identified
00:07:53.05: URL context #1 will be used
00:07:53.05: Performing URL search on: ldap:///l%3DSGSIN%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg))
00:07:53.05: mmc_read_url result: [uid=mailtes1,ou=People,ou=ZZZ,ou=Customers, l=SGSIN, o=portnet.com]
00:07:53.05: URL resolution returned: [uid=mailtes1,ou=People,ou=ZZZ,ou=Customers, l=SGSIN, o=portnet.com]
00:07:53.05: mmc_read_url result: [mail] [email protected]
00:07:53.05: URL resolution returned: [mail] [email protected]
00:07:53.05: Attribute index: 16
00:07:53.05: LDAP URL produced address [email protected]
00:07:53.05: mmc_read_url result: [mail] [email protected]
00:07:53.05: URL resolution returned: [mail] [email protected]
00:07:53.05: Attribute index: 16
00:07:53.05: LDAP URL produced address [email protected]
00:07:53.05: No more result to return
*** Debug output from rewriting a forward envelope address:
00:07:53.05: Rewriting: Mbox = "mailtes1", host = "portnet.com.sg", domain = "$*", literal = "", tag = ""
00:07:53.05: Rewrite: "$*", position 0, hash table -
00:07:53.05: Found: "$E$F$U%[email protected]$V$H"
00:07:53.05: Match, pattern = "portnet.com.sg", current = "(*domaincheck*)"
00:07:53.05: old state = not checked.
00:07:53.05: Domain check on portnet.com.sg.
00:07:53.05: Added domain result 1 to cache for portnet.com.sg.
00:07:53.05: new state = succeeded.
00:07:53.05: New mailbox: "mailtes1".
00:07:53.05: New host: "portnet.com.sg".
00:07:53.05: New route: "png1app1-mail.portnet.com.sg".
00:07:53.05: New channel system: "png1app1-mail.portnet.com.sg".
00:07:53.05: Looking up host "png1app1-mail.portnet.com.sg".
00:07:53.05: - found on channel l
00:07:53.05: Routelocal flag set; scanning for % and !
forward channel = l
channel description =
channel user filter =
dest channel filter =
source channel filter =
channel flags #0 = BIDIRECTIONAL MULTIPLE IMMNONURGENT NOSERVICEALL
channel flags #1 = NOSMTP DEFAULT
channel flags #2 = COPYSENDPOST COPYWARNPOST POSTHEADONLY HEADERINC NOEXPROUTE
channel flags #3 = LOGGING NOGREY NORESTRICTED RETAINSECURITYMULTIPARTS
channel flags #4 = EIGHTBIT NOHEADERTRIM NOHEADERREAD RULES
channel flags #5 = SLAVE_DEBUG
channel flags #6 = LOCALUSER REPORTNOTARY
channel flags #7 = NOSWITCHCHANNEL NOREMOTEHOST DATEFOUR DAYOFWEEK
channel flags #8 = NODEFRAGMENT EXQUOTA REVERSE NOCONVERT_OCTET_STREAM
channel flags #9 = NOTHURMAN INTERPRETENCODING USEINTERMEDIATE RECEIVEDFROM VALIDATELOCALSYSTEM NOTURN
defaulthost = portnet.com.sg portnet.com.sg
linelength = 1023
channel env addr type = SOURCEROUTE
channel hdr addr type = SOURCEROUTE
channel official host = png1app1-mail.portnet.com.sg
channel queue 0 name = LOCAL_POOL
channel queue 1 name = LOCAL_POOL
channel queue 2 name = LOCAL_POOL
channel queue 3 name = LOCAL_POOL
channel after params =
channel user name =
urgentnotices = 1 2 4 7
normalnotices = 1 2 4 7
nonurgentnotices = 1 2 4 7
channel rightslist ids =
local behavior flags = %x7
expandchannel =
notificationchannel =
dispositionchannel =
saslswitchchannel =
tlsswitchchannel =
backward channel = l
header To: address = [email protected]
header From: address = [email protected]
envelope To: address = [email protected] (route (png1app1-mail.portnet.com.sg,png1app1-mail.portnet.com.sg)) (host portnet.com.sg)
envelope From: address = [email protected]
name =
mbox = mailtes1
Results of ./imsimta test -rewrite -debug mailtes1 on ims52 as follows:
*** Debug output from rewriting a forward header address:
00:09:58.97: Rewriting: Mbox = "mailtes1", host = "portnet.com.sg", domain = "$*", literal = "", tag = ""
00:09:58.97: Rewrite: "$*", position 0, hash table -
00:09:58.97: Found: "$E$F$U%[email protected]$V$H"
00:09:58.97: Rewrite failed, not envelope.
00:09:58.97: Rewrite: "$*", position 1, hash table -
00:09:58.97: Failed.
00:09:58.97: Rewrite: "$*", position 0, rewrite database -
00:09:58.97: Failed
00:09:58.97: Rewriting: Mbox = "mailtes1", host = "portnet", domain = "portnet.com.sg", literal = "", tag = ""
00:09:58.97: Rewrite: "portnet.com.sg", position 0, hash table -
00:09:58.97: Found: "$U%[email protected]"
00:09:58.97: New mailbox: "mailtes1".
00:09:58.97: New host: "portnet.com.sg".
00:09:58.97: New route: "pnsasit1app1.portnet.com".
00:09:58.97: New channel system: "pnsasit1app1.portnet.com".
00:09:58.97: Looking up host "pnsasit1app1.portnet.com".
00:09:58.97: - found on channel l
00:09:58.97: Routelocal flag set; scanning for % and !
00:09:58.97: Rewrite rules result: [email protected]
00:09:58.97: Checking reverse URL cache for: [email protected]
00:09:58.97: Applying reverse URL pattern ldap:///$V?mail?sub?$Q to: [email protected]
00:09:58.99: Resulting URL: ldap:///l%3Dsgsin%2Co%3Dportnet.com?mail?sub?(|([email protected])([email protected]))
00:09:58.99: mmc_open_url called to open ldap:///l%3Dsgsin%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg)), flags = 256
00:09:58.99: URL with quotes stripped: ldap:///l%3Dsgsin%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg))
00:09:58.99: LDAP URL identified
00:09:58.99: URL context #1 will be used
00:09:58.99: Performing URL search on: ldap:///l%3Dsgsin%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg))
00:09:58.99: mmc_read_url result: [email protected]
00:09:58.99: URL resolution returned: [email protected]
forward channel = l
channel description =
channel user filter =
dest channel filter =
source channel filter =
channel flags #0 = BIDIRECTIONAL MULTIPLE IMMNONURGENT NOSERVICEALL
channel flags #1 = NOSMTP DEFAULT
channel flags #2 = COPYSENDPOST COPYWARNPOST POSTHEADONLY HEADERINC NOEXPROUTE
channel flags #3 = LOGGING NOGREY NORESTRICTED RETAINSECURITYMULTIPARTS
channel flags #4 = EIGHTBIT NOHEADERTRIM NOHEADERREAD RULES
channel flags #5 = SLAVE_DEBUG
channel flags #6 = LOCALUSER REPORTHEADER
channel flags #7 = NOSWITCHCHANNEL NOREMOTEHOST DATEFOUR DAYOFWEEK
channel flags #8 = NODEFRAGMENT EXQUOTA REVERSE NOCONVERT_OCTET_STREAM
channel flags #9 = NOTHURMAN INTERPRETENCODING USEINTERMEDIATE RECEIVEDFROM VALIDATELOCALSYSTEM NOTURN
defaulthost = portnet.com.sg portnet.com.sg
linelength = 1023
channel env addr type = SOURCEROUTE
channel hdr addr type = SOURCEROUTE
channel official host = pnsasit1app1.portnet.com
channel queue 0 name = LOCAL_POOL
channel queue 1 name = LOCAL_POOL
channel queue 2 name = LOCAL_POOL
channel queue 3 name = LOCAL_POOL
channel after params =
channel user name =
urgentnotices = 1 2 4 7
normalnotices = 1 2 4 7
nonurgentnotices = 1 2 4 7
channel rightslist ids =
local behavior flags = %x7
backward channel = l
header To: address = [email protected]
header From: address = [email protected]
envelope To: address = [email protected] (route (pnsasit1app1.portnet.com,pnsasit1app1.portnet.com)) (host portnet.com.sg)
envelope From: address = [email protected]
name =
mbox = mailtes1
emails sent to mailtes1 using the Sun messaging 2005q4 service will be en-queued as '[email protected]' for sender but de-queued to mail store with '[email protected]' as sender.
09-Dec-2007 21:00:47.38 tcp_intranet ims-ms E 1 [email protected] rfc822;[email protected] mailtes1@ims-ms-daemon
09-Dec-2007 21:00:48.19 ims-ms D 1 [email protected] rfc822;[email protected] mailtes1@ims-ms-daemon
Physical message file will show '[email protected]' as sender.
Return-path: <[email protected]>
Received: from portnet.com.sg (pnsgsit1app2.portnet.com [10.106.65.36])
by mailsit.portnet.com.sg
(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
with ESMTP id <[email protected]> for
[email protected]; Sun, 09 Dec 2007 21:00:47 +0800 (SGT)
Received: from [10.106.65.101] (Forwarded-For: 10.10.140.109)
by mailsit.portnet.com.sg (mshttpd); Sun, 09 Dec 2007 21:00:47 +0800
Date: Sun, 09 Dec 2007 21:00:47 +0800
From: [email protected]
Subject: test
To: [email protected]
Message-id: <[email protected]>
MIME-version: 1.0
X-Mailer: Sun Java(tm) System Messenger Express 6.2-8.04 (built Feb 28 2007)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7bit
Content-disposition: inline
X-Accept-Language: en
Priority: normal
Original-recipient: rfc822;[email protected]
test
Action tried.
1) Re-order values of mail attribute as follows:
mail: [email protected]
[email protected]
results from ./imsimta test -rewrite -debug mailtes1 on Sun messaging 2005q4:
*** Debug output from rewriting a forward header address:
00:21:45.57: Rewriting: Mbox = "mailtes1", host = "portnet.com.sg", domain = "$*", literal = "", tag = ""
00:21:45.57: Rewrite: "$*", position 0, hash table -
00:21:45.57: Found: "$A$E$F$U%[email protected]"
00:21:45.57: Rewrite failed, not envelope.
00:21:45.57: Rewrite: "$*", position 1, hash table -
00:21:45.57: Failed.
00:21:45.57: Rewrite: "$*", position 0, rewrite database -
00:21:45.57: Failed
00:21:45.57: Rewriting: Mbox = "mailtes1", host = "portnet", domain = "portnet.com.sg", literal = "", tag = ""
00:21:45.57: Rewrite: "portnet.com.sg", position 0, hash table -
00:21:45.57: Found: "$U%[email protected]"
00:21:45.57: New mailbox: "mailtes1".
00:21:45.57: New host: "portnet.com.sg".
00:21:45.57: New route: "mailsit.portnet.com.sg".
00:21:45.57: New channel system: "mailsit.portnet.com.sg".
00:21:45.57: Looking up host "mailsit.portnet.com.sg".
00:21:45.57: - found on channel l
00:21:45.57: Routelocal flag set; scanning for % and !
00:21:45.57: Rewrite rules result: [email protected]
00:21:45.57: Checking reverse URL cache for: [email protected]
00:21:45.57: Applying reverse URL pattern ldap:///$V?mail?sub?$Q to: [email protected]
00:21:45.58: Resulting URL: ldap:///l%3DSGSIN%2Co%3Dportnet.com?mail?sub?(|([email protected])([email protected]))
00:21:45.58: mmc_open_url called to open ldap:///l%3DSGSIN%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg)), flags = 384
00:21:45.58: URL with quotes stripped: ldap:///l%3DSGSIN%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg))
00:21:45.58: LDAP URL identified
00:21:45.58: URL context #1 will be used
00:21:45.58: Performing URL search on: ldap:///l%3DSGSIN%2Co%3Dportnet.com?mail?sub?(|([email protected])(mailAlternateAddress=mailtes1@portnet.
com.sg))
00:21:45.59: mmc_read_url result: [uid=mailtes1,ou=People,ou=PSA,ou=Customers, l=SGSIN, o=portnet.com]
00:21:45.59: URL resolution returned: [uid=mailtes1,ou=People,ou=PSA,ou=Customers, l=SGSIN, o=portnet.com]
00:21:45.59: mmc_read_url result: [mail] [email protected]
00:21:45.59: URL resolution returned: [mail] [email protected]
00:21:45.59: Attribute index: 16
00:21:45.59: LDAP URL produced address [email protected]
00:21:45.59: mmc_read_url result: [mail] [email protected]
00:21:45.59: URL resolution returned: [mail] [email protected]
00:21:45.59: Attribute index: 16
00:21:45.59: LDAP URL produced address [email protected]
00:21:45.59: No more result to return
*** Debug output from rewriting a forward envelope address:
00:21:45.59: Rewriting: Mbox = "mailtes1", host = "portnet.com.sg", domain = "$*", literal = "", tag = ""
00:21:45.59: Rewrite: "$*", position 0, hash table -
00:21:45.59: Found: "$A$E$F$U%[email protected]"
00:21:45.59: Match, pattern = "portnet.com.sg", current = "(*domaincheck*)"
00:21:45.59: old state = not checked.
00:21:45.59: Domain check on portnet.com.sg.
00:21:45.59: Added domain result 1 to cache for portnet.com.sg.
00:21:45.59: new state = succeeded.
00:21:45.59: New mailbox: "mailtes1".
00:21:45.59: New host: "portnet.com.sg".
00:21:45.59: New route: "mailsit.portnet.com.sg".
00:21:45.59: New channel system: "mailsit.portnet.com.sg".
00:21:45.59: Looking up host "mailsit.portnet.com.sg".
00:21:45.59: - found on channel l
00:21:45.59: Routelocal flag set; scanning for % and !
forward channel = l
channel description =
channel user filter =
dest channel filter =
source channel filter =
channel flags #0 = BIDIRECTIONAL MULTIPLE IMMNONURGENT NOSERVICEALL
channel flags #1 = NOSMTP DEFAULT
channel flags #2 = COPYSENDPOST COPYWARNPOST POSTHEADONLY HEADERINC NOEXPROUTE
channel flags #3 = LOGGING NOGREY NORESTRICTED RETAINSECURITYMULTIPARTS
channel flags #4 = EIGHTBIT NOHEADERTRIM NOHEADERREAD RULES
channel flags #5 = MASTER_DEBUG SLAVE_DEBUG
channel flags #6 = LOCALUSER REPORTNOTARY
channel flags #7 = NOSWITCHCHANNEL NOREMOTEHOST DATEFOUR DAYOFWEEK
channel flags #8 = NODEFRAGMENT EXQUOTA REVERSE NOCONVERT_OCTET_STREAM
channel flags #9 = NOTHURMAN INTERPRETENCODING USEINTERMEDIATE RECEIVEDFROM VALIDATELOCALSYSTEM NOTURN
defaulthost = portnet.com.sg portnet.com.sg
linelength = 1023
channel env addr type = SOURCEROUTE
channel hdr addr type = SOURCEROUTE
channel official host = mailsit.portnet.com.sg
channel queue 0 name = LOCAL_POOL
channel queue 1 name = LOCAL_POOL
channel queue 2 name = LOCAL_POOL
channel queue 3 name = LOCAL_POOL
channel after params =
channel user name =
urgentnotices = 1 2 4 7
normalnotices = 1 2 4 7
nonurgentnotices = 1 2 4 7
channel rightslist ids =
local behavior flags = %x7
expandchannel =
notificationchannel =
dispositionchannel =
saslswitchchannel =
tlsswitchchannel =
backward channel = l
header To: address = [email protected]
header From: address = [email protected]
envelope To: address = [email protected] (route (mailsit.portnet.com.sg,mailsit.portnet.com.sg)) (host portnet.com.sg)
envelope From: address = [email protected]
name =
mbox = mailtes1
emails sent to mailtes1 using the Sun messaging 2005q4 service will be en-queued as '[email protected]' for sender and de-queued to mail store with '[email protected]' as sender.
10-Dec-2007 00:20:00.88 tcp_intranet ims-ms E 1 [email protected] rfc822;[email protected] mailtes1@ims-ms-daemon
10-Dec-2007 00:20:01.63 ims-ms D 1 [email protected] rfc822;[email protected] mailtes1@ims-ms-daemon
Physical message file will show '[email protected]' as sender.
But this time the recipient is '[email protected]'
Return-path: <[email protected]>
Received: from portnet.com.sg (pnsgsit1app2.portnet.com [10.106.65.36])
by mailsit.portnet.com.sg
(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
with ESMTP id <[email protected]> for
[email protected]; Mon, 10 Dec 2007 00:20:00 +0800 (SGT)
Received: from [10.106.65.101] (Forwarded-For: 10.10.140.109)
by mailsit.portnet.com.sg (mshttpd); Mon, 10 Dec 2007 00:20:00 +0800
Date: Mon, 10 Dec 2007 00:20:00 +0800
From: [email protected]
Subject: test mail from ims62
To: [email protected]
Message-id: <[email protected]>
MIME-version: 1.0
X-Mailer: Sun Java(tm) System Messenger Express 6.2-8.04 (built Feb 28 2007)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7bit
Content-disposition: inline
X-Accept-Language: en
Priority: normal
Original-recipient: rfc822;[email protected]
test
Questions:
1) How do i retain the functionality of using 1st value of the mail attribute as the address to be used?
I need the address reversing to retain '@portnet.com.sg' value.
2) I've not encountered the same problem when using ims52.
Is there a functional diffences here?

Hi Shane,
Thank you for the reply.
We tried adding a mailequivalentaddress attribute, eg [email protected] but the From field still have the value from the mail attribute, eg [email protected]. Do we still need to configure anything to make this to work?
Besides we tried another option by doing the following:
a. Changing the following lines in options.dat file:
REVERSE_URL=ldap:///$V?mail?sub?$Q
to
REVERSE_URL=ldap:///$V$N?sub?$R
b. We ensure that '@portnet.com.sg' is the 1st value
c. adding a 'noreverse' keyword for the 'ims-ms' channel
And it works without the need for the mailequivalentaddress, is this a proper implementation?
any implications with putting 'noreverse' for ims-ms channel?
We're now considering changing of primary address attribute used.
Need your advise on the following:
1) Please advise how go about configuring another attribute to store the primary address.
2) Can we use mailAlternateAddress as the new primary address attribute?
If a totally new attribute is needed, please advise on the requirements for the creation of this attribute to be usable by Sun Messaging 2005Q4.
This change was mentioned in the administration guide.
Chapter 9 The Direct LDAP Algorithm and Implementation
Seeding the Reversal Cache
Next the primary address and any aliases attached to the user entry are considered. This information is used to seed the address reversal cache. It plays no part in the current address translation process. First, the primary address, personal name, recipient limit, recipient cutoff, and source block limit attributes are considered. The primary address is normally stored in the �mail� attribute; another attribute can be specified by setting the LDAP_PRIMARY_ADDRESS MTA option appropriately. (The primary address reverses to itself, of course.) There is no default attribute for any of the other attributes. If you want to use them, you must specify them with the LDAP_PERSONAL_NAME, (see Vacation Autoreply Attributes) LDAP_RECIPIENTLIMIT, LDAP_RECIPIENTCUTOFF, (see Limiting Message Recipients) and LDAP_SOURCEBLOCKLIMIT (see Specifying Absolute Message Size Limits) MTA options. The corresponding domain-level recipient limit, recipient cutoff, and source block limit attributes are also considered at this point. User-level settings completely override any domain-level setting.
Next, any secondary addresses are considered and a cache entry is made for each one. There are two sorts of secondary addresses: Those that undergo address reversal and those that do not. Both must be considered in order to properly seed the address reversal cache because of the need to check for message capture requests in all cases.
Secondary addresses that undergo reversal are normally stored in the mailAlternateAddress attribute. Another attribute can be specified by setting the LDAP_ALIAS_ADDRESSES MTA option. Secondary addresses that do not undergo reversal are normally stored in the mailEquivalentAddress attribute. Another attribute can be specified with the LDAP_EQUIVALENCE_ADDRESSES MTA option.
Edited by: sheeyong on Dec 10, 2007 5:25 AM

Incorrect data value when insert into oracle table

Would like to ask expert here, how could I insert data into oracle table where the value is 03 ? The case is like that, the column was defined as varchar2(50) data type, and I have a csv file where the value is 03 but when load into oracle table the value become 3 instead of 03.

user11432758 wrote:
Would like to ask expert here, how could I insert data into oracle table where the value is 03 ? The case is like that, the column was defined as varchar2(50) data type, and I have a csv file where the value is 03 but when load into oracle table the value become 3 instead of 03.
implicit datatype conversion to NUMBER can result in leading zero to be eliminated.
How do I ask a question on the forums?
https://forums.oracle.com/message/9362002#9362002

Incorrect Goods value when crediting an incorrect MIRO invoice

Dear all,
There is one thing I do not understand.
My customer is on the coffee business, both selling and producing coffee.
Normally they get two inovices for every purchase order, since the price of coffee is changing a lot. Normally the original invoice is coming first (before the goods is received), then an invoice of the price adjustment and then the goods is received.
The price adjustment (invoice number 2) should not affect the stock value and therefore it is registered in transaction MIRO with antoher document type than original invoices. Now the price adjustment inovvoice was registered before the original invoice and with the same document type as normal invoices. Then the original invoice was also registered. The customer wanted to credit the first invoice but what happened? Since the value of the goods have been affected a much higher price is credited and the difference is posted to the "loss under covera ccount (P/L account). But I do not want that posting!
This is what happaned:
1) Price adjustment invoice, debit goods recievied/invoice recieved account 10 000 EUR, 20 000 PIECES
2) Original Invoice, debit goods recievied/nvoice recieved account 100 000 EUR, 20 000 PIECES
3) Credit of price adjustment, Credit goods recievied/invoice recieved account 50 000 EUR, 20 000 PICES AND debit 40 000 EUR on account "loss stock under cover"
But I do not want to have any posting on the P/L account "loss stock under cover" and I would also like to have a credit of 10 000 EUR on goods recievied/invoice recieved account , not another amount. I know this is due to material valuation but is there a way to solve this?
Best Regards,

Solved!

CO-PA: value field correction due to miscalculated SD condition value

HI,
we are using ECC 60 SP11. Due to incorrect condition value calculation in SD this condition value (only used in CO-PA) is posted on a CO-PA value field causing wrong CO-PA results.
As the SD document (invoice) will not be changed anymore a reversal/reposting in CO-PA (ke4s) does not solve the problem.
My idea of value correction (only in CO-PA, I do not care about KEAT in that case...) is to use RKECADL1 to logical delete the old documents and to create a LSMW for ke21n to repost the documents again with the right value for the affected value field.
The question is, the document reference of the old (wrong) CO-PA document shows the billing document and its logical deleted by RKECADL1. My new document does not have a document reference to this billing document as the document source is ke21n.
Any idea how to "change" the document reference in a way that document flow for the billing document shows the ke21n-created document (with the right condition value)?? If I don not change it, document flow will not show any CO-PA document for that case (the old one is logical deleted, the ke21n-doc. is not linked to it)
I want avoid manual changes in Ce1**** as its a dirty solution and I am not completely sure if/which other tables are affected.
Best regards, Christian

The only way to effect the document flow is to cancel and repost the document. if that is not possible then KE21N - Create Line Items will fix your issue in COPA but this will not appear in billing. You can enter data fields that coonect to billing doc etc.
pts appreciated.

Transfer condition values with +/- signs to CO-PA (Explain the purpose)

Dear Sap guru's,
Could you please guide me on the below issue, We make a new condition type zne1 which is excise duty free items, Based on cleint requirement. a/c entry like this ( example )
10) 210 ea            net value 23,153.04 cost 21,600.00
20) 0 ea              net value 0               cost 2400
           Customer AC           DR 20163 Rs
           Excise duty payble   Cr 432 -
           Sales                      Cr 22721-
           vat payable              cr 3010-
           excise duty payble   cr 48-
           Excise duty free       cr 48-
           Excise duty free       dr 48
           sales                       dr 48
Here client pay the excise duty for free goods issue items, For this situation what ever the amount he paid in the excise duty free item that same amount he wants to reduce in sales ie it should be debit in my exaple it is 48 rs.
My problem is i configured ZNE1 condtion assgined to value filed ERLOS. While release to a/c system returns "CHEK VALUE FILED ASSIGNEMENT TO CONDITION TYPE". when I make the settings +/- sign for the conditon system allow me to release and save. Please guide me whithout assignment how to release billing document?
Regards
Maruthi

Hi
Conditions from SD are always transferred to CO-PA with "+" signs, with the exception of credit memos and returns. The reasons for this is that the signs for revenues are handled differently in the different applications of the R/3 System. For example, revenues are positive in SD, while they are negative in FI. Consequently, CO-PA accepts all the values as positive, and then subtracts deductions and costs from revenues in the information system.
This configuration needs to be done in the system if you have the CO-PA active and the SD flows are configured. Unfortunately you will not be able to ignore this. Please see below some SAP help snippets for your benefit.
Note that certain limitations exist on the transfer of condition values of billing documents to CO-PA.
1. To transfer condition types for sales revenues and sales deductions to CO-PA, you need to make sure that the condition types and linked to an account in FI that is also defined as a cost element of the category "11" (revenue element) or "12" (sales deduction) in CO. These condition types must be assigned to a CO-PA value field.
Condition types linked to FI accounts that are defined as cost elements of another category are not transferred to CO-PA, even when the condition type has been assigned to a CO-PA value field.
2. Condition types such as "VPRS" ("Cost") that are defined as statistical in SD are always transferred to CO-PA if they are assigned to a value field.
3. All condition types that you want to transfer to CO-PA must be active in the SD pricing procedure. Inactive conditions in a billing item are not transferred. If all the conditions in a billing item are inactive, that item is not transferred to CO-PA.
Conditions do not need to be active, however, to be transferred with sales order items, since the transfer of incoming sales orders is always statistical.
It is also possible to transfer conditions from MM to update billing data in pooled payment in the IS Retail system. These are transferred according to the same rules as SD conditions
Hope it was helpful.
Karthik

Edit condition value of service entry sheet

hi,
is there any way to change the service conditions value at the time of invoice verification. there is no seggregation of condition value when enter invoice for services.

Hi,
System posted difference / values in GR/IR services account based on condtion maintained in system ,the effect will takes place after the SES gets final acceptance. So system capturing condition values in MIRO-Invoice varification based on Posted SES .
If value seems wrong then revoke ses ,make changes or adjust the value with the help of Subsequest Credit /Subsequent Debit/ with Credit memo.
Hope this will be helpful.
Thanks & Regards,
Sandesh Sawant

Condition Values different fro Billing and Excise Invoice in some cases

Hi All,
Excise Invoice for domestic sales is having different condition values.
I am scenerio like this when Billing doc manually VF01, excise Invoice in generated automatically and condition values
were corrrect.But when I create Billing Document using BAPI in program, Excise Invoice is not generating,then
we are running BDC for T-code J1IIN and creating Excise Invoice.Excise Invoice generated in second case (by BDC)
is having wrong condition values.
Can anyone explain why it is happing.Is there any user exist to copy Billing Doc condition values to Excise Invoice?
Thanks in Advance ,
Rayudu

Thanks for you response Lakshimipathy.
The above mentioned configurations were all ready done.Excise Invoice is getting generated when we create Billing Doc online.
Problem here is Excise invoice is not getting generated automatically when Billing Doc is created by our program,so we were running BDC code to created excise Invoice.
Condition values ( Duties :AED,Ecess,SHEcess) were getting calculated wrongly in excise Invoice which is created by running BDC code in program. But the Excise invoice which was created automatically while saving Billing doc manually is having correct condition values. But the billing document condition values remain the same & correct for both.
Regards,
Rayudu

Preventing billing split for multiple deliveries (over-riding billing date)

Hi all,
I have multiple deliveries which should be invoiced into ONE billing document. The only difference between the deliveries is the billing date, which is why it is splitting.
I am therefore copying routine 001 and in VOFM and adding this code to the end of it:
vbrk-fkdat = sy-datum. "prevent split due to difference in billing date
This is great and working fine because when I have 2 deliveries with diff. billing dates, it will take todays date. The only problem is when:
1. Billing for a single document (dated 11/08/2011), it will over-write it and set the date to today (17/08/2011)
2. Billing for 2 documents with the same date
What is the best way around this?
Thanks

Dear Pistols123,
1. Billing for a single document (dated 11/08/2011), it will over-write it and set the date to today (17/08/2011)
Here can't you write the code to check whether there is only one billing document, if so omit your code for the date manipulation.
So that system will not assign system date, but will take the orginal date (actual good issue date or billing date entered in vf01)
2. Billing for 2 documents with the same date
write the code to check whether all the billing documents have the same date , if so omit your code for the date manipulation.
So that system will not assign system date, but will take the orginal date (actual good issue date or billing date entered in vf01)
Thanks & Regards,
Hegal K Charles

Bill of Lading and multiple deliveries

Hi Guru's,
I have a question regarding Bill of Lading and deliveries. We can have multiple deliveries which are related to one Bill of Lading. Normally when I process the per delivery the DESADV IDOC but is there another way to send multiple deliveries based on the same Bill of Lading?
Best regards,
Guido Koopmann

If you mean that you'd like to have multiple deliveries i one IDoc then it's not feasible. Unless you create a custom IDoc, of course. To my knowledge, there is no IDoc for bill of lading. Shipment is pretty much the only document that may include multiple deliveries.
But if you just want to select the deliveries by BOL # and create individual DESADV IDocs for them, then it should be feasible, at least by writing a small "wrapper" ABAP report.

Condition value not updated when qty changed

hi all,
I have created a new condition ZPR1 (copied from PR00) and use a new formula for it.
There is a problem when I change the qty after the item is billed.
Suppose the original qty is 1 and total ZPR1 price is 100. When I change the qty to 2, the ZPR1 price is still 100! It will change to 200 if the item is not billed.
Anybody encounters such problem and how to solve?
Thanks

Hi,
I don't mean to change the unit price.
I mean the condition value (the item total price) is not updated
You can't change the price anymore in the condition tab after you billed
But when you change the qty of the item, the total value should change accordingly
And I think for my case I should not cancel the invoice. Suppose original qty is 10, and there is partial shipment of 7 and billed the customer. Later customer request to reduce the qty to 7 to complete the item. We should not cancel the invoice in this case.
Try to test with PR00 and PN00, you will see the item value will be changed according to the item qty.

Cumulative quantity has exceeded still billing have condition value.

Hi,
Requirement – One discount condition which will be applicable up to a certain quantity at billing.
Issue – Condition is getting determined at billing while cumulative quantity has exceeded.( I am using pricing type C in copy control delivery to billing).
Note –     1. I am using partial Delivery method.
               2. When creating new order functionality is working fine.
Existing Scenario-
i. I have created one condition with condition update setting.
ii. I have maintained VK11 with amount 90 Rs. and Max.cond.base value 1000 qty in additional data.
iii. I have created one sales order (ord. qty. 1500).
iv. Created 1st delivery and billing for 1000 qty.
v. When creating 2nd billing(qty 200) with same delivery, system is picking discount condition which should not happen as billing quantity has exceeded.
Please advise
Thanks and Regards,
Vinod

Hi Vinod,
Which routine have you created..did u create a routine for 'alt calc type' or 'alt cond base value' in pricing ?
If after using A or D in pricing type in copy control, the condition values are not copied from the sales order, then that means there is some issue with the copying control settings.
Anyways, now you have met your requirement.
Please close this discussion.
Regards
Jobi

Incorrect Condition Values when billing multiple deliveries

Similar Messages

Maybe you are looking for