Hello Imran,
Adding a separate Line Item for the Material in Delivery will not work. What you can do is create a Delivery Split using VLSP. You can learn more about Delivery Splitting on SAP Help.
↧
Re: Add new line item in delivery process for billing
↧
Re: Add new line item in delivery process for billing
Dear Gurus,
What i feel feasible in this scenario as per my overall situation.
user go to the order create another line for the same material and call the line item 20 in the outbound delivery manually by selecting the outbound delivery drop down > deliver sales order.
Regards,
imran khan
↧
↧
Re: Combination of multiple order into one invoice based on PO number at Item level
Hi,
just use copy control VTFA.
BR
Robert
↧
Re: Combination of multiple order into one invoice based on PO number at Item level
Hi Ashish,
1. Use VTFA
2. Maintain Routine 003 in the field of VBRK/VBRP
Please check where u get expected output or not.
Regards,
Arnab
↧
Re: Combination of multiple order into one invoice based on PO number at Item level
my documents are getting split due to creation date of sales order, how to remove that criteria so that it will not take creation date as split criteria.
↧
↧
How to avoid invoice splitting for a particular sales organization based on creation date of sales order?
Hello Gurus,
I want to avoid invoice split, I have 2 orders and creation date is different so how can I combine these two order. It is order related billing.
Please help.
Regards,
Ashish Arora
↧
Re: How to avoid invoice splitting for a particular sales organization based on creation date of sales order?
Hi Ashish,
You have to do some coding for the same in the t code VOFM . Go T code VTFA and check the header . Copy requirement.
Regards,
Arnab
↧
Re: Error - Assign Condition Type to CO-PA Value Field
Hi Alex,
Thanks for your reply.
I am checking the note 20254 as mentioned by you. I shall check the details and revert.
Regards
Ratna
↧
Re: Combination of multiple order into one invoice based on PO number at Item level
Hi Ashish,
As per standard SAP rule if you have two different dates then according to the spliting rule your sales order must be split. So for your requirement not to be split you need to talk with ABAPer who will give you the proper solution how to achieve this goal.
Regards,
Arnab
↧
↧
Re: How to avoid invoice splitting for a particular sales organization based on creation date of sales order?
Hi arora ashish,
I never heard that order creation date can lead to invoice split.
Please see note 11162 (invoice split criteria in billing document).
May I know what is showing in invoice split analysis?
Best Regards,
Tao
↧
Re: How to avoid invoice splitting for a particular sales organization based on creation date of sales order?
Not sure whether you already had tested and found invoice split has happened based on creation date. As rightly said, invoice split would not have happened due to creation date. Recheck and update this.
G. Lakshmipathi
↧
Re: Combination of multiple order into one invoice based on PO number at Item level
Ashish,
You will have to write an ABAP condition in the copy control routine and use the SAP provided field VBRK- ZUKRI to combine the invoices based on the desired condition.
Thanks,
Ravin
↧
IDCP - Check/ Lock on same Lot & Book Number ended (multiple user)
Hi Experts,
Need help regarding this one as I cant find SAP OSS related on end of check on Lot and Book on IDCP .
It is our requirement that Official doc Number in IDCP shall be unique per invoice
Issue: Official Doc Number XXX internal auto generated) on Lot 01 & Book 01 ( has been assigned to Invoice A by "first user "using IDCP. After the print icon been hit/ or possibly still printing, it seems the check/ lock on the Book/Lot Number ended. Making it possible for another user to enter the IDCP and the system proposed same Official Doc Number XXX for Invoice B which 2nd user tries to print.
Note: the issue happened After the print icon been hit/ or possibly still printing.
Before printing, the check / lock still exist (error Book 01 in Lot 01 blocked by user __2nd)
This matter of few seconds system permission caused the issue.
Initially assigning Official Doc Number XXX to Invoice A
But after print of Invoice B - reassigning Official Doc Number XXX to Invoice B
making Invoice A reference to be 00000000.
Please advise how to fix the issue.
a. should prohibit the Permission of system for 2nd user to enter to IDCP whenever 1st user is still inside transaction
or
b. Correct proposal of suggested official doc number +1.
Your thoughts?
Regards
D.
Already checked , any else?
IDCP reseting the field Reference (XBLNR) to zeros
This is a common situation when you use IDCP solution for Chile. IDCP solution is using an already assigned number from a different Lot Number. The situation happens when the customer have the same number for different Lot Number. The case is possible because each type of operation (like billing sales, credit note or debit note) has a different Lot Number (Folio) for different areas in the company or in the company's division.
In order to solve this problematic scenario, follow the instructions shown in the SAP KBA 1895971
↧
↧
Too many data fields selected(greater than 200 bytes) in v/03
Hi all,
I am getting error while creating condition table for A715 IN V/03. .i.e is Too Many data fields selected (greater than 200 bytes) in V/03. How to solve this.
↧
Re: Too many data fields selected(greater than 200 bytes) in v/03
Hi,
This restriction exists due to field VAKEY.
Keep in mind that field VAKEY is limited to 100 Char in the SAP systems ( this 100 char matches with an internal length of 200 bytes in an Unicode system)
And unfortunately there is no possibility to extend that domain through SP or notes.
The internal length of this field is 200 bytes in pricing (A) tables.
You can check the internal length in SE11, table A000:
Internal length 200 <<
Since the required length is greater, the error message occurs.
You have the possibility to change the size of the data element. This would, however, be a modification (note 170183).
The other solution is to reduce the number of fields.
Best Regards,
Tao
↧
Re: To remove invoice documents from blocked list of accounting
Hi Brian,
I tried with VBRK-RFBSK to C in debugging mode. However i am facing error as pricing procedure ZCC200 isnot exits in T683 table . we have checked entry in T683 .It is there. because of it, i cannt edit value in table. Any more advice on it please
Br
Sachin Karale
↧
not able to copy manual conditions from quotation to sales order for APO materials
Hi,
manual conditions are not copied from quotation to sales order for APO materials.where as i am able to copy manual conditions from quotaion to sales order for normal materials.
I have already applied configuration changes as per SAP note no 451108 for TAPA item category. I ta is very urgent, kindly reply ASAP.
Regards
↧
↧
Automatic invoice in the back ground
Hi,
I have seen a BAPI to create invoice and it is working fine for me.
BAPI_BILLINGDOC_CREATEMULTIPLE
The client requirement is they do not want to create Invoice manually,they want to do it automatically.They will only do PGI for deliveries.Once PGi is done ,Invoice needs to created in back ground.
Is there any back ground job available to create Invoice.
↧
Re: Automatic invoice in the back ground
Hi Thambi Durai,
I am not sure whether this can fulfill your requirement, but you can use VF06 to schedule invoice creation job in background.
Best Regards,
Tao
↧
Re: To remove invoice documents from blocked list of accounting
Hi Sachin
You can make the change with this report. Put it in your test system or a production copy and test it. Change the check on the user name to your SAP ID and you will be the only person ever able to run this. Once you have made the change to satisfy your business and your audit requirements you can remove the report from your system. It runs in test mode if you set the DB_Upd flag = 'X' it will write the value you maintain in the screen field 'status' to the VBRK-RFBSK field so you set either 'C' or 'E' to drop it of the worklist.
Kind regards
Brian
REPORT Z_RFBSK.
TABLES: VBRK.
DATA: BEGIN OF XVBRK OCCURS 1.
INCLUDE STRUCTURE VBRK.
DATA: END OF XVBRK.
* Werte eingeben; Datenbankänderung, wenn DB_UPD <> blank
PARAMETERS: DOCUMENT LIKE VBRK-VBELN DEFAULT '00000000',
status like vbrk-rfbsk default 'C',
DB_UPD(1) DEFAULT ' '.
* Only the authorised user can run this report
* check sy-uname = 'SUPERUSER'.
* Positionsstatus in interne Tabelle schreiben und dort ändern
SELECT * FROM VBRK INTO TABLE XVBRK WHERE VBELN = DOCUMENT.
LOOP AT XVBRK.
if XVBRK-rfbsk is initial.
move status to XVBRK-rfbsk.
endif.
MODIFY XVBRK.
ENDLOOP.
* interne Tabelle auf Datenbank schreiben
IF DB_UPD = ' '.
WRITE: / 'no change in database for this document', DOCUMENT.
ELSE.
UPDATE VBRK FROM TABLE XVBRK.
WRITE: / 'change of posting status', DOCUMENT.
ENDIF.
↧