Billing CDR prefix Error Billing CDR prefix Error Billing CDR prefix Error

Thank you for your help.
i have this question, My AS5400 send CDR for my Billing System ... but the calls or CDR for incoming national calls (Mobile & Fix)to my network are coming without prefix for our local and national calls which is 00962, on other hand calls from my network to other local carriers include the prefix 00962...is it clear?
All other International calls include correct prefixes no problem.
Example:
Local Mobile= 0777223344
Local Fix= 064536543
my network= 063000000
Jordan Prefix= 962
Now call from o777223344 or 064536543
to 063000000 has the error where CDR at Billing system without 00962 it is only 063000000 it is not 96263000000 this take us that call comes from Phillipines Fix 63 and not from my network 63000000.
Remember calls from 063000000 to any destination is right prefix.
any help please at AS5400 or PGW2200??

Hi,
Without knowing if you are using switched or nailed PGW config, I can say there are 2 solutions. One on the PGW
and one on the 5400. You can choose which solution fits you the best.
PGW Nailed solution:
Setup a bmoddig in a dialplan to prefix 962 to any number coming in starting with 63
Apply custgrpid to incoming ss7path.
#### creates the dialplan ####
numan-add:dialplan:custgrpid="lma3", OVERDEC="YES"
#### digits to prefix ####
numan-add:digmodstring:custgrpid="lma3",name="add962",digstring="962"
### result set for dialplan ####
numan-add:resultset:custgrpid="lma3",name="addpre"
#### modify the b number starting at the beginning and add the digits specified in digmodstring ####
numan-add:resulttable:custgrpid="lma3",name="addprefix",resulttype="BMODDIG",dw1="1",dw2="0",dw3="add962",setname="addpre"
#### Route based on B number starting with digits 63 ####
numan-add:bdigtree:custgrpid="lma3",callside="originating",digitstring="63",setname="addpre"
#### Apply custgrpid to incoming ss7path ####
prov-ed:sigsvcprop:name="ss7path",custgrpid="lma3"
### Deploy config ####
prov-dply
Restart of PGW software may be needed.
PGW switched solution:
Setup a bmoddig in a dialplan to prefix 962 to any number coming in starting with 63
Apply custgrpid to incoming ss7 trunkgrp.
#### creates the dialplan ####
numan-add:dialplan:custgrpid="lma3", OVERDEC="YES"
#### digits to prefix ####
numan-add:digmodstring:custgrpid="lma3",name="add962",digstring="962"
### result set for dialplan ####
numan-add:resultset:custgrpid="lma3",name="addpre"
#### modify the b number starting at the beginning and add the digits specified in digmodstring ####
numan-add:resulttable:custgrpid="lma3",name="addprefix",resulttype="BMODDIG",dw1="1",dw2="0",dw3="add962",setname="addpre"
#### Route based on B number starting with digits 63 ####
numan-add:bdigtree:custgrpid="lma3",callside="originating",digitstring="63",setname="addpre"
#### Apply custgrpid to incoming ss7 trunkgrp ####
prov-ed:trnkgrpprop:name="1000",custgrpid="lma3"
### Deploy config ####
prov-dply
Restart of PGW software may be needed.
NAS Solution:
Create a voice translation rule to prefix 962 to 63 number.
Apply to incoming pots voice port
voice translation-rule 1
rule 1 /\(^63\)/ /962\1/
voice translation-profile add962
translate called 1
voice-port 2:D
translation-profile incoming add962

Similar Messages

Error while creating Billing doc using VF01 for Debit memo req. from RRB

Hi,
I am creating billing doc for my Debit memo req. which is created using RRB(DP90, DP95).
Error message - Item 000010 does not exist.
When I debugged and looked into code it seems following lines are causing problem.
Program
LV60AA28
Line u2013 734
IF vbap-vkgru EQ vkgru_dyn_posten.
    IF vbap-aufnr IS INITIAL .
set AUBEL because it was overwritten by VBAP-VBELN
      vbrp-aubel = vbap-vgbel.
      vbrp-aupos = vbap-vgpos.
      vbrp-autyp = vbap-vgtyp.
This code was not in 4.6 system.
We have just migrating from 4.6 to 6.0 and facing this issue while testing.

First of all you should try to learn how to express in a public forum like this.
On your comments
Do some ground work from your end
why should I ?? if you want you can do ground work or any work. If you post a question, you have to hear patiently all suggestions and dont scribble whatever you want.
You should have some basic
   understanding of SAP ABAP.
You should have posted this question ABAP forum !!!!   Why without any sense you have posted in sales forum ??

Error while releasing Billing document in Subcontract process

Hi All,
We are working on Subcontract process as explained below:
Company code X purchases the component A and sends it to Company code Y on Subcontract. Company codes X and Y belongs to one company using single operative chart of Accounts, Controlling area & operating concern. FI configuration has been maintained in OBYA by treating above company codes Inter company GLs. The component A is sent to company code Y as non value added item. Through 501 movement type, as the component is sent by Company code X.
Company code Y will add some components (like B,C and charges some expenses as service component D for preparing Finished good) and send this FG to Company code X. For this company code Y will raise a Sales order and followed by MRP run and Production order is created.
In VA02 of above Sales Order, while entering Item details, where the Settlement rule is asking for PA Transfer structure (in Account assignment tab of Item details) and giving the following error analysis:
Enter a PA transfer structure
Message no. KD 044
Diagnosis
A PA transfer structure is required for settlement to profitability analysis.
System Response
You cannot save this settlement rule.
Procedure
Enter a PA transfer structure. To do this, choose the "Parameters" function in the settlement rule. As part of customizing, you can also store a default value for the PA analysis structure, in the settlement profile. The system then uses this default value when you enter a settlement rule.
In addition to above, another issue has raised while releasing the Billing document after doing PGI. Accounting document is not getting generated and while releasing the Billing document (VF02) it is throwing an error as
Enter profitability segment as cost object for Revenue and COGS posting
Message no. ZC 001.
MM,PP,SD & FICO configuration settings maintained:
1. All required OBYC settings
2. All cost element and Cost element categories have been maintained
3. From MM side the system is generating FI & CO documents
4. Settlement profile in Production Order type is maintained (in KOT2). Allocation structure and PA transfer structure were maintained in (OK06, OK07 & KEI1). In PA transfer structure we have assigned the required Sources and Value fields and settlement cost elements.
5. In VKOA condition types KOFI and KOFK were maintained for relevant Customer & Material Account Assignment groups.
6. Required settings have maintained in OKB9.
Movement types 501 (sub contract), Received back to Company code X through Movement type 101. In spite of these settings still we are getting the above mentioned errors.
Could any one help to provide some inputs on the above issue as early as possible.
Thanks in advance.

Hi,
check in the sales order line item procurement tab . u can get the requirement type. in SPRo check the requiremnt class for the requirement type. in that requirement clas u will get settrlemnt profile for the sales order. Check that settlemnt profile there u have to maintain the PA transfer structure.
I think both problem will get solved by maintaing the PA structure..
You are doing sales order costing right....and i hope it is non vsaluated sales order costing .....
If help ful please assign points.
cheers
Prabhat

Vf02 error while releasing a billing doc to accounting

Hello All,
I m getting the below mentioned error while releasing a billing doc for a accouting.
I have checked all the settings in vkoa , ob52 and many more and all are set properly, now m not able to track where actually the prob is.
error is: No account is specified in item 0000001004
Message no. F5670
Diagnosis
No account was specified for account type "S" in item "0000001004" of the FI/CO document.
System Response
The Financial Accounting program cannot process the document.
Procedure
A system error has probably occurred in the application you called up. Check the data transferred to item "0000001004" of the FI/CO document.
Points wil be rewarded
Thanks,
SUnny

Hi,
Have you checked what is the determination account determination log ? You can do this by entering in VF02 and select from the menu Environment -> Account Determination Analisys -> Revenue Accounts.
In this log you can see what are posting keys determined from the pricing procedure that should be posted in the FI document and determine very easy in which step the account was not determined.
After that you can maintain the correct account in VKOA transaction.
BR,
Valentin

Error while saving the billing document

Dear All,
I am getting an Error- "No taxes on sales/purchase are allowed for account 870205 L002, AB is not allowed" when i save the billing document. when i go to the conditions tab under item data in the billing document after saving the document and try to view the detail for the discount condition type it shows that the discount condition type has a tax code AB assigned to it.
I am using the same pricing procedure in another company code where it works fine and I don't get any error. Besides here on viewing the same discount condition type there is no tax code assigned.
Can anybody explain what could be the possible reason?
I searched for the solution in the forum and came to know that if I go to FS00 and assign * to Tax Category under control data then it works fine and i don't encounter the problem after saving the billing document.
Although i have found the solution But what troubles me is that when the same pricing procedure works fine in the first company code without assigning * to the tax category then why do i need to assign * in the second company company code to be able to save the billing document.
Thanks and Regards
Deepak Joshi

First of all let me ask you to indicate the name correctly.
Secondly, the root cause to the issue what you have indicated is in FS00 and you need to compare the settings in both the company codes.
Finally, the issue is not because of your pricing procedure but because of some missing FI settings. Thats all I can say now based on the information you have provided.
thanks
G. Lakshmipathi

Error while releasing the Billing document

Hi Everyone,
Encountering an error with the description 'Balance in Transaction currency' while trying to release the Billing document from VF02 transaction, still didnt come across the right oss note that can remove this error, can any one give me a clue on this,
Rgds,

hi,
We are facing similar problem, when releasing the billing document to accounting.
Have you been able to find the solution to this problem. If so, kindly suggest the answer
Thanks
Dinesh

Error while creating a billing (no accounting document gnerated)

hi gurus,
while saving a billing document in vf01 error pops up no accounting document generated and when i go to account determination analysis in billing tax condition is missing
kindly help me out
thanks

hi
then goto VF02 and from the menu Environment--Account determination analysis-revenue acccounts
find here whether any assignment is missing
check u r VKOA settings whether the g/l ACCOUNT HAS assigned or not for that tax condition type
regards

Tax code error while releasing a billing document to accounting in VF02

Hi SAP Gurus,
While trying to release a billing document to accounting, the following error is displayed
" Tax Statement Item Missing for Tax Code TA".
Message number: FF805.
Please provide your valuable inputs to overcome this issue.
Suitable points shall be rewarded.
Thanks and Regards,
Sreeni.

Check your pricing procedure. One of the Tax relevant items is ending up with a base value of Zero.
This is easy to check if you double-click on tax related Pricing Conditions, you will find one of them with a base value is zero.
If not, it could be something more simpler, like GL Account master data. Make sure the "Post without tax allowed" box is checked and ensure the tax category is masked ("*").
Hope this helps.
Cheers.

Error while releasing a billing document to accounting.

Hi Guys,
I have a billing document and i am trying to release it to accounting but we are not able to do it. We are getting an error
System error in routine FI_TAX_GET_TXJCD_LEVELS error code 2 function builder TAX2
Message no. FF769
We are on SAP ECC 6.0.
any idea how to resolve this issue? I have looked into many OSS notes but was not able to find anything close.
Cheers
VJ

Hi Vijayendra,
Were you able to solve this issue? We have the same thing happening and was wondering if you could help me here.
Thanks.
regards,
Raj

Error while releasing Billing doc to Accounting

Hi all
I am gettin the following error while releasing a Billing doc to FI-
Reconciliation account 240001 or short key 00 is not permitted
The Billing doc pertains to Export sales and the billing Doc type is Export Invoice. However the Customer Recon A/c is defined as 240000 which is for Domestic Sales. A/c 240001 stands for Export Sales. I am wondering why it is asking for the Export Sales Recon a/c. Does this has something to do with Alternative Recon A/c? Should I set an Alternative Recon A/c and check this? If yes, then should it be defined in SD or FI?
If any1 has come across this prob, plzz help me.
Regards

It is all Fi related, and should be defined by the Fi Consultant.
But by changing the sort key I think your error can be solved. But I don't exactly know your config settings to recommend any solution.
Regards
AK
Please reward if helpful

Error in creation of billing document: update was terminated

hi experts,
i am facing one problem while creating "Billing Document" in VF01 . After i save it says 'Document 941700032 has been saved' but later after i click on tht it shows d error "update was terminated' and billing document no i not getting created .
Thanks

After save, and during SAP's update processing, a fatal error occured, causing a rollback of the transaction. Since the user is no longer in that same transaction at this point, SAP issues the Express Document to attempt to inform that there was a failure. Check ST22 for abend...in the meantime, check for exit coding that may be causing an error...In my previous life, working with SD/LE at lot, I was able to get these regularly by fouling up my exit coding....lol.

Error in creation of Phantom item bill

Hi Gurus,
We have planned to use phantom item. for that wehave created an item of type: 'option class'. Then created its routing but facing below error when trying to cretae bill for phantom item.
Kindly help me out
Regards,
Ali Raza
APP-FND-01048: Use of this combination restricted by WHERE clause ' ( ((:parameter.query_mode = 2 AND bom_enabled_flag = 'Y') OR (:parameter.query_mode = 1 AND EXISTS (SELECT NULL FROM bom_bill_of_materials bom WHERE bom.organization_id = :parameter.org_id AND bom.assembly_item_id = inventory_item_id AND ((:parameter.bom_or_eng = 1 AND assembly_type = 1) OR :parameter.bom_or_eng = 2) ))) AND (bom_item_type in (:parameter.model_item_access, :parameter.planning_item_access, :parameter.std_item_access, :parameter.oc_item_access) ) AND ((:parameter.bom_or_eng = 1 AND eng_item_flag = 'N' AND NOT EXISTS (SELECT 'X' FROM bom_bill_of_materials bom WHERE bom.organization_id = :parameter.org_id AND bom.assembly_item_id = inventory_item_id AND bom.alternate_bom_designator IS NULL AND bom.assembly_type <> 1) AND (:parameter.eam_type is null OR (:parameter.eam_type in (1, 2, 3)
APP-FND-01388: Cannot read value for profile option FND_INDICATOR_COLORS in routine &ROUTINE.

Hi Sandeep,
Thanks for your reply.
I have checked all three possibilities. Item is not Engineering item and already assigned to Org. Also the BOM doesnot exist. Kindly note that I donot have any issue in creating bill of a standard item. We are using phantom item for the first time so tell me if phantom item need some special setup or some profile option to be active etc? I am using below attributes in inventory. Kindly go through it and suggest.
Deviation Factor +     0
Deviation Factor -     0
Shelf Life Days     0
Price Tolerance %     0
Acceptable Rate -     0
Acceptable Rate +     0
Postprocessing Lead Time     0
Planning Time Fence Days     1
Lead Time Lot Size     1
Descriptive Flexfield     ---------
Item Status     Active
Conversions     Both standard and item specific
Forecast Control     Consume Forecast
Effectivity Control     Date
Service Request     Enabled
RMA Inspection Required     Inspection not required
Default SO Source Type     Internal
Restrict Locators     Locators restricted to pre-defined list
Make or Buy     Make
Billing Type     Material
Cycle Count Enabled     No
Check Material Shortage     No
Lot Split Enabled     No
Lot Merge Enabled     No
Lot Translate Enabled     No
Lot Substitution Enabled     No
Bulk Picked     No
Engineering Item     No
EAM Notification Required     No
Use Approved Supplier     No
Taxable     No
Allow Description Update     No
RFQ Required     No
Outside Processing Item     No
Equipment     No
Planned Inventory Point     No
Repetitive Planning     No
Build in WIP     No
Customer Ordered     No
Customer Orders Enabled     No
Internal Ordered     No
Internal Orders Enabled     No
OE Transactable     No
Assemble to Order     No
Ship Model Complete     No
Financing Allowed     No
Invoiceable Item     No
Invoice Enabled     No
Enable Contract Coverage     No
Enable Defect Tracking     No
Lot Control     No lot control
Serial Number Generation     No serial number control
Lot Expiration     No shelf life control
End Assembly Pegging     None
Check ATP     None
ATP Components     None
Safety Stock     Non-MRP planned
Inventory Planning Method     Not planned
MRP Planning Method     Not planned
Primary Unit of Measure     NUMBER
BOM Item Type     Option class
WIP Supply Type     Phantom
User Item Type     Phantom item
Locator Control     Prespecified locator control
Tracking UOM Indicator     Primary
Pricing UOM Indicator     Primary
Reservable     Reservable
Restrict Subinventories     Subinventories restricted to pre-defined list
Description     TEST FG
Revision Control     Under revision quantity control
Planning Time Fence     User-defined time fence
Inventory Item     Yes
Stockable     Yes
Transactable     Yes
BOM Allowed     Yes
Costing Enabled     Yes
Inventory Asset Value     Yes
Include in Rollup     Yes
Purchased     Yes
Purchasable     Yes
Receipt Required     Yes
Create Supply     Yes
Shippable     Yes
Pick Components     Yes
Returnable     Yes
Enable Service Billing     Yes
Regards,
Ali Raza

Account determination error in FI doc during SD billing doc posting.

hi,
when I create one billing doc ref to s/o,
I check account determination in condition type:
G/L account no.: 110000
Provision acc. : 120000
in FI doc,
should debit 110000 and credit 120000
but current status is credit 110000 and debit 120000
Please help.
Thanks.

Hi,
One of the following could be the reasons for the Account determination error.
Please check.
1.Incorrect account assignment group entered in the customer and material master
Resolution:Maintain correct account assignment group in customer and material master,Eg.External Domestic,Z1 - External Foreign,Internal Foreign,etc,.
2.GL account not extended to the respective company code.
Resolution:Extend the required GL account to the company code.
Regards,
Sophia Xavier

Account determination error in Billing

Dear Expert,
I create one billing doc(1840000318) based on SO:1810000296. But in the posting status it is showing "Posting document not created(account determn error) in billing. I did not found any FI relavant docs for this billing in open item customer list.
*Anyone can advice me why the FI docs not created automatically..???
**Do you think there any missing configuration set?
***Or if I cancel the billing docs then it will okay or not ?
Thanks & b.Rgds
Bishnu

Hi Bishnu,
Check Points for Account Determination.
1. Ensure Cutomer master (Xd02)Sales Area Data- Billing Tab-- Acc Assign Grp ---Should be maintained
2. Material Master -
Sales Org-2----
Acc Assign Grp..Should be maintained.
3. In VKOA maintain
Application- V Chart of Accounts--Sales Org ---Acc Assgn Gp Of Cust -Acc Assgn Gp of Material-Acc Keys (ERL,ERS,ERF)----& G/L Account.
4. In ur Pricing Procedure i.e V/08... Maintain Reqt -2 corresponding to ERL,ERS,ERF. & Subtotal =9 in front of net total.
Revert for further clarification.
Regards
Amit Gupta

Error in Updating Billing Docs

Hi Gurus,
When i'm updating the some billing docts in VBOF, the system thros the "No correction due to value change" error.
Can u tell me what is the problem?
cheers,
Sumith

Hi Sumith,
The billing document may be having accounting doc, so the system is telling that correction should not be done with related to value of the invoice.
If you reverse that accounting doc ment you can able to change the Invoice.
I hope it will help you
Thanks,
Murali.

Billing CDR prefix Error Billing CDR prefix Error Billing CDR prefix Error

Similar Messages

Maybe you are looking for